Don't re-clone Standbys on every reboot #5
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
davissp14
changed the title
davissp14
force-pushed
the
dont-reclone-on-reboot
branch
from
a90267b to
02c6c9f
Compare
davissp14
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Notables:
Primary/Standby registrations are now forced on reboot, this will rewrite the record within
repmgrand seems to be required to pick up any changes made to therepmgr.conffile.We are only cloning from the primary if we are a new standby or if we are a recovering primary ( that's no longer primary).
cc:// @DAlperin