Replicator stop retrying to read when cursor is already closed #239
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.
Motivation
Replicator's ManagedCursor gets closed when replicator is deleted from the policies. However, as Removing Replicator for a topic is not performed atomically and because of that sometimes, replicator-producer tries to read from Cursor which already Closed. In that case, replicator should not retry to read the message again (because replicator is already removed and cursor is closed for that replicator) and consider
CursorAlreadyClosedExceptionas non-retriable exception, close the producer and stop the replicator.Modifications
Replicator considers
CursorAlreadyClosedExceptionas non-retriable exception so, it stops retrying further read and closes the producer.Result
PersistentReplicator will not retry read on
CursorAlreadyClosedException.