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] Do not health check streams that are actively being restored. #4277

Merged
merged 2 commits into from Jun 29, 2023

Conversation

derekcollison
Copy link
Member

Could leave them in a bad state.

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

Resolves #4270

Could leave them in a bad state.

Signed-off-by: Derek Collison <derek@nats.io>
Signed-off-by: Derek Collison <derek@nats.io>
@derekcollison derekcollison requested a review from a team as a code owner June 28, 2023 23:17
@derekcollison derekcollison merged commit 503de45 into main Jun 29, 2023
2 checks passed
@derekcollison derekcollison deleted the fix-4270 branch June 29, 2023 00:48
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.

R3 stream restore incorrectly fails with stream name already in use, cannot restore (10130)
2 participants