diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-09 00:08:14 +0000 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-09 00:08:14 +0000 |
commit | ed4df05ce917d6cf175aeb508b0485ae5f281a0a (patch) | |
tree | 9313abd8fd41a78eb2bf1ffd0f95f10b69cd25cb /doc/administration/geo/disaster_recovery/background_verification.md | |
parent | 1bdb3fe3821fc3d222361d8b2e2ec2fea2915372 (diff) | |
download | gitlab-ce-ed4df05ce917d6cf175aeb508b0485ae5f281a0a.tar.gz |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/geo/disaster_recovery/background_verification.md')
-rw-r--r-- | doc/administration/geo/disaster_recovery/background_verification.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/administration/geo/disaster_recovery/background_verification.md b/doc/administration/geo/disaster_recovery/background_verification.md index 2caaaac2b9d..6852d08cc07 100644 --- a/doc/administration/geo/disaster_recovery/background_verification.md +++ b/doc/administration/geo/disaster_recovery/background_verification.md @@ -17,7 +17,7 @@ You can restore it from backup or remove it from the **primary** node to resolve If verification succeeds on the **primary** node but fails on the **secondary** node, this indicates that the object was corrupted during the replication process. Geo actively try to correct verification failures marking the repository to -be resynced with a backoff period. If you want to reset the verification for +be resynced with a back-off period. If you want to reset the verification for these failures, so you should follow [these instructions][reset-verification]. If verification is lagging significantly behind replication, consider giving @@ -114,9 +114,9 @@ Feature.enable('geo_repository_reverification') ## Reset verification for projects where verification has failed Geo actively try to correct verification failures marking the repository to -be resynced with a backoff period. If you want to reset them manually, this +be resynced with a back-off period. If you want to reset them manually, this rake task marks projects where verification has failed or the checksum mismatch -to be resynced without the backoff period: +to be resynced without the back-off period: For repositories: |