Remove orphan ledger when managedCursor fails to switch ledger #350
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
Due to #336 issue, multiple brokers own same topic and it cause
KeeperException.BadVersionException
in broker when it tries to update cursorInfo with newly created ledger. Broker is not deleting created ledger and it exist without cursor reference. So, such orphan ledgers creates leak when broker fails to update cursor info.Modifications
Handle cursorInfo failures and delete newly created ledger.
Result
It prevents ledger leak if broker fails to update cursor-info.