geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-2806) when batch is dispatched, if the bucket is not primary, we should still destroy the event from queue
Date Fri, 21 Apr 2017 16:59:04 GMT

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

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

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

GEODE-2806: if the batch is dispatched, even the bucket is no longer primary, the batch should
still be deleted as planned.


> when batch is dispatched, if the bucket is not primary, we should still destroy the event
from queue
> ----------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-2806
>                 URL: https://issues.apache.org/jira/browse/GEODE-2806
>             Project: Geode
>          Issue Type: Bug
>            Reporter: xiaojian zhou
>            Assignee: xiaojian zhou
>              Labels: lucene
>
> This is one of the root causes for data mismatch. 
> When AEQ dispatched a batch, when it tried to destroy the events from queue, the bucket
might be no longer primary. There's no need to let the new primary to re-dispatch the batch.




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

Mime
View raw message