forked from hazelcast/hazelcast
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Because of the behaviour change introduced in hazelcast#16303, when the requested sequence is larger than the largest sequence (tailSequence) + 1, we don't listen from the oldest sequence (headSequence) but rather from the tailSequence + 1. Both approaches are fine and both approaches work better in some scenarios. Since the listener is loss tolerant, we can skip items from headSequence..tailSequence+1 anyway. Fixed the test to adhere to the new behaviour. We assume that eventually as we publish an item, it will reach the listener. A better fix would be to introduce unique IDs per ringbuffer, where we would then be able to distinguish between a completely lost ringbuffer and a ringbuffer which has not received the last few items and appropriately reset the requested sequence to the headSequence or tailSequence. Fixes: hazelcast#16430
- Loading branch information
Matko Medenjak
committed
Jan 8, 2020
1 parent
0a19592
commit 9584a09
Showing
1 changed file
with
20 additions
and
38 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters