NRG: Don't delete RAFT state if stream/consumer creation failed during shutdown #6061
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.
Antithesis found a case where if a server was hard killed and would replay RAFT append entries during startup, if it would then be SIGTERM-ed while the RAFT recovery is running, the
acc.lookupStream
that happens injs.processClusterCreateStream
resulted in aJetStream not enabled for account
error. Which would then delete the RAFT state.There are also other errors that could pop up, so either way; if we're shutting down, don't delete the RAFT state.
Signed-off-by: Maurice van Veen github@mauricevanveen.com