Fix a fug where repl-backlog-size config was modifed in keydb.conf with the runtime change during the config rewrite #698
Conversation
This file contains 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
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.
There was a bug where original
repl-backlog-sizeconfig value was overwritten by the config rewrite command received by the sentinel during the master/ replica switchover.Basically, the
repl-backlog-sizewas resized to twice its original value when the usage was insufficient, and hence it was resized to therepl-backlog-disk-resevein runtime.@JohnSully As discussed in the yesterday's meeting, this PR should resolve the above problem, and we have verified the fix on our end as well.
@JohnSully / @msotheeswaran could you please review and merge? thanks.
@paulmchen @hengku @yzhao244