Geo - Repository verification on secondary node
What does this MR do?
Initial implementation of verifying repository/wikis on the Geo pecondary node using checksums calculated on the Geo primary node and verified on the secondary.
Are there points in the code the reviewer needs to double check?
This MR depends on https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4428
Why was this MR needed?
To support better disaster recovery, planned failovers, and data integrity
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary - [-] Documentation created/updated
- [-] API support added
-
Tests added for this feature/bug - Review
- [-] Has been reviewed by UX
- [-] Has been reviewed by Frontend
-
Has been reviewed by Backend -
Has been reviewed by Database
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together - [-] Internationalization required/considered
- [-] If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan
-
End-to-end tests pass ( package-qa
manual pipeline job)
What are the relevant issue numbers?
Related to https://gitlab.com/gitlab-org/gitlab-ee/issues/5064
Edited by Stan Hu