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

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

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

GEODE-2939: Make sure bucket region initiate event tracker from the image 
provider.

Save all event states from remote processes.
Initiate event tracker from the image provider only.


> Initiate bucket event tracker and get GII from different source could lead to 
> bucket copies inconsistence
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-2939
>                 URL: https://issues.apache.org/jira/browse/GEODE-2939
>             Project: Geode
>          Issue Type: Bug
>          Components: regions
>            Reporter: Eric Shu
>            Assignee: Eric Shu
>              Labels: storage_2
>
> When a bucket region is created, it send CreateRegionMessage to all nodes 
> hosting the bucket data. It initiates its event tracker from the first one 
> replied. 
> In one case, it copies event tracker states from the node with primary 
> bucket, which is processing putAll operation and already applied a few entry 
> operations (so the newer seqNo is recorded for the thread performing the 
> putAll). 
> However, it gets initial image from another node -- which does not have the 
> entry operations yet (as putAll op is not yet being distributed to secondary 
> yet.)
> The newly created region would receive all the putAll operations from the 
> primary when the primary distributes the putAll operations to secondary 
> copies. In the node with newly created region, some of the events would not 
> be applied due to hasSeenEvent method call (up to initiated last seqNo for 
> the said thread). This leads to bucket inconsistence among the redundant 
> copies.
> Please note this issue would not occur if there is only one redundant copy.



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

Reply via email to