geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-1609) Events missing from Lucene index when a bucket moves and is moved back during dispatching
Date Thu, 07 Jul 2016 17:09:11 GMT


ASF subversion and git services commented on GEODE-1609:

Commit 7b28a8d4e9dc4359d4d11d286f895537864f3a03 in incubator-geode's branch refs/heads/develop
from [~upthewaterspout]
[;h=7b28a8d ]

GEODE-1558, GEODE-1609: Fixing failures due to rebalancing buckets during lucene index updates

There are two failures we're fixing here:
1) Calling repository.create for create events was leaving duplicate events in the
index because when a bucket fails over, the event is dispatched again on the new primary.
Using the isPossibleDuplicate flag did not work because it was not consistently set to
true for duplicate events. Changed the code to call repository.update even for create events

2) The async event queue was repeatedly dispatching the same events event after
a bucket moved to another node. We changed the async event queue code to filter out
events for buckets that are no longer present on this dispatching member.

Cleaning up the rebalancing test and adding new tests to make these scenarios
more reproducable.

This closes #176

> Events missing from Lucene index when a bucket moves and is moved back during dispatching
> -----------------------------------------------------------------------------------------
>                 Key: GEODE-1609
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: lucene
>            Reporter: Dan Smith
> While working on GEODE-1558, we added a test of moving a bucket during dispatching, and
then having the new dispatcher move the bucket back when it tries to dispatch.
> In this case the entry that is in that bucket never makes it to the lucene index.
> The test is sitting on this feature branch:
> To see the failure, remove the "@Ignored" annotation from LuceneQueriesPRBase.returnCorrectResultsWhenBucketIsMovedAndMovedBackOnIndexUpdate
and run the test.

This message was sent by Atlassian JIRA

View raw message