[jira] [Created] (GEODE-2900) BucketRegionQueue transitions from primary/secondary/primary can lead to events lingering in queue

["Jason Huynh (JIRA)" <ji...@apache.org>]

Jason Huynh created GEODE-2900:
----------------------------------

             Summary: BucketRegionQueue transitions from primary/secondary/primary can lead to events lingering in queue
                 Key: GEODE-2900
                 URL: https://issues.apache.org/jira/browse/GEODE-2900
             Project: Geode
          Issue Type: Bug
          Components: wan
            Reporter: Jason Huynh


In this scenario when peek() is called from BucketRegionQueue, a side effect is that the key is removed from the eventSeqNumQueue and an event is placed into the peekedEvents list.

If there is failure dispatching the event, we add the peekedEvents list to a new peekedEvents list.  Before doing so, we remove any events that we are not primary for.  Now the event is not in the eventSeqNumQueue or the peekedEvents list

If we now become primary (before the other node could dispatch this event), and because we do not have that event in the eventSeqNumQueue or the peekedEvents, it gets "stuck."




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)