Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.8.2, 1.9.0
Description
When the emitter reaches the max timestamp for the current queue, it stops emitting and waits for the max timestamp to advance. Since it simultaneously selects the next queue as the new "minimum" queue, it may deadlock if the previous min queue represents the new global lower bound after the max timestamp advanced. This occurs very infrequently and we were finally able to reproduce.