[FIXED] Stream peers drift after server peer-remove #6720
Merged
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.
If a server is peer-removed, a new peer will be selected if the server hosted a stream. That new peer would be given the new peer set by the meta layer, but would then reset back to the old peer set as part of the stream's log.
This is a short-term fix, proposing the new peer set through the stream's log to ensure all replicas agree on it.
Later we'll need to rework some parts to ensure the meta layer only 'suggests' new changes, but the proposing actually goes through the stream/consumer's log instead of meta's log.
Signed-off-by: Maurice van Veen [email protected]
Co-authored-by: Neil Twigg [email protected]