Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FIXED] A peer-remove of an R1 could brick the stream. #4420

Merged
merged 1 commit into from Aug 23, 2023
Merged

Conversation

derekcollison
Copy link
Member

We should not remove a peer from a stream when we can not find a replacement unless R>1.

Signed-off-by: Derek Collison derek@nats.io

Resolves #4396

Signed-off-by: Derek Collison <derek@nats.io>
@derekcollison derekcollison requested a review from a team as a code owner August 23, 2023 00:57
@derekcollison derekcollison merged commit 5a926f1 into main Aug 23, 2023
2 checks passed
@derekcollison derekcollison deleted the fix-4396 branch August 23, 2023 03:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

nats stream cluster peer-remove puts R1 stream in non-recoverable state
2 participants