[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=16097020#comment-16097020 ] 

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

Commit acdf2e80184edf9c3ba934a6f0fa760a83020953 in geode's branch refs/heads/develop from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=acdf2e8 ]

GEODE-2900: DUnit test of moving primary during AEQ dispatching

Adding a dunit test that moves the primary and moves it again during AEQ
dispatching.

This closes #506


> 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: lucene, wan
>            Reporter: Jason Huynh
>            Assignee: Jason Huynh
>             Fix For: 1.2.0
>
>
> 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 also affects the Lucene implementation.  An stuck event can mean incorrectly indexed data or data inconsistencies



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)