Memberlist now forwards only changes, not full original received message #4419
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.
What this PR does: This PR modifies memberlist KV client such that when it receives message via
NotifyMsg
, which changes current state of the KV store, it doesn't forward entire message, but only sub-message with changes. This helps in some clusters to get rid of unwanted messages with tombstones, which currently DO generate a change (this is bug, PR incoming) and then retransmit even the part of message that hasn't changed anything. This can in some situations bring back ingester instances in the ring, which should be long forgotten.Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]