[
https://issues.apache.org/jira/browse/GEODE-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005664#comment-16005664
]
ASF GitHub Bot commented on GEODE-2900:
---------------------------------------
GitHub user upthewaterspout opened a pull request:
https://github.com/apache/geode/pull/506
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.
@jhuynh1 - I based this test on top of your PR for GEODE-2900. Feel free
to merge it in if the test looks good to you. This test fails without your
changes and passes with those changes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/upthewaterspout/incubator-geode
feature/GEODE-2900-test
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/geode/pull/506.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #506
----
commit 7cf0be13ed2abe9a707a2b4fe0ded66f0870da77
Author: Dan Smith <upthewatersp...@apache.org>
Date: 2017-05-10T23:32:05Z
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.
----
> 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
>
> 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.3.15#6346)
