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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GEODE-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003084#comment-16003084 ] 

ASF subversion and git services commented on GEODE-2900:
--------------------------------------------------------

Commit 240b469ff217fbfba39381f196ae3e0e832a69a6 in geode's branch refs/heads/feature/GEODE-2900 from [~huynhja]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=240b469 ]

GEODE-2900:  push shadow key back into the front of the eventSeqNumber "Queue"


> 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
>            Assignee: 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)