diff options
| author | Evan Read <eread@gitlab.com> | 2019-07-16 22:02:27 +0000 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2019-07-16 22:02:27 +0000 |
| commit | e26d99329699ca550a2f1c21bbb1f4c481425085 (patch) | |
| tree | 0ffc5251db6a7ffb30a90ab89fa0de211258410c | |
| parent | 1cb21ec289a223fe30d2d8977f4dd0238b24c6da (diff) | |
| parent | a5ca1e488d350d48a42f757a765835dc1bf4663d (diff) | |
| download | gitlab-ce-e26d99329699ca550a2f1c21bbb1f4c481425085.tar.gz | |
Merge branch '12812-geo-update-current-limitations-of-background-verification-docs' into 'master'
Geo - Update current limitations for automatic background verification
Closes gitlab-ee#12812
See merge request gitlab-org/gitlab-ce!30688
| -rw-r--r-- | doc/administration/geo/disaster_recovery/background_verification.md | 17 |
1 files changed, 12 insertions, 5 deletions
diff --git a/doc/administration/geo/disaster_recovery/background_verification.md b/doc/administration/geo/disaster_recovery/background_verification.md index 8eee9427b56..27866b7536e 100644 --- a/doc/administration/geo/disaster_recovery/background_verification.md +++ b/doc/administration/geo/disaster_recovery/background_verification.md @@ -171,14 +171,21 @@ If the **primary** and **secondary** nodes have a checksum verification mismatch ## Current limitations -Until [issue #5064][ee-5064] is completed, background verification doesn't cover -CI job artifacts and traces, LFS objects, or user uploads in file storage. -Verify their integrity manually by following [these instructions][foreground-verification] -on both nodes, and comparing the output between them. +Automatic background verification doesn't cover attachments, LFS objects, +job artifacts, and user uploads in file storage. You can keep track of the +progress to include them in [ee-1430]. For now, you can verify their integrity +manually by following [these instructions][foreground-verification] on both +nodes, and comparing the output between them. + +In GitLab EE 12.1, Geo calculates checksums for attachments, LFS objects and +archived traces on secondary nodes after the transfer, compares it with the +stored checksums, and rejects transfers if mismatched. Please note that Geo +currently does not support an automatic way to verify these data if they have +been synced before GitLab EE 12.1. Data in object storage is **not verified**, as the object store is responsible for ensuring the integrity of the data. [reset-verification]: background_verification.md#reset-verification-for-projects-where-verification-has-failed [foreground-verification]: ../../raketasks/check.md -[ee-5064]: https://gitlab.com/gitlab-org/gitlab-ee/issues/5064 +[ee-1430]: https://gitlab.com/groups/gitlab-org/-/epics/1430 |