rabbit_stream_coordinator: Handle delete_stream idempotently #14884
+30
−4
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.
Within
rabbit_stream_coordinator:delete_stream/2, the stream could be successfully deleted from the stream coordinator but the update to the metadata store (rabbit_amqqueue:internal_delete/2) could fail separately. If this happens then subsequent attempts to delete the stream also fail because the coordinator did not reply todelete_streamrequests for unknown stream IDs.This change has the stream coordinator reply
okwhen it receives adelete_streamcommand and the stream isundefined. This would let thedelete_stream/2continue and remove the lingering state from the metadata store.Fixes #14852