fixes #419 NoSuchElementException during race condition in PartitionState #422
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.
In busy situations, there is a race condition in PartitionState due to it being edited by the Controller, and read by the BrokerPoller.
Because the check and subsequent read of the incompleteOffsets collection are two different operations, it can initially appear as though it has elements, but when we try to retrieve an element, it can then be empty, which throws a NoSuchElementException.
Thanks to a very elegant fix suggested by @shaileshkulkarni, we can combine the check and retrieval by using the thread safe #ceiling method, which can either returns the #first element, or null if empty.
This is as opposed to the more brute force solution which would require using locks.
This, among other things, will be made redundant once #200 (a shared nothing architecture) is merged.
Description...
Checklist