Update documentatiton on how to enable strong consistency
What does this MR do?
Starting with Gitaly 13.3, reference transactions are enabled by default with a primary-wins strategy. While Gitalies will now vote on reference updates by default, this still doesn't enable strong consistency as the primary will always succeed no matter what secondaries vote for. As a result, an admin now only has to change the voting strategy to not use the primary-wins strategy in order to enable strong consistency.
This MR adjusts the documentation to match this.
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team