You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/04/18 23:44:00 UTC
[jira] [Commented] (GEODE-5103) During rebalance, a client node may
miss a transactional event
[ https://issues.apache.org/jira/browse/GEODE-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443354#comment-16443354 ]
ASF subversion and git services commented on GEODE-5103:
--------------------------------------------------------
Commit b4a315e92cf024c2c9beabf982d515f472786187 in geode's branch refs/heads/feature/GEODE-5103 from [~eshu]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b4a315e ]
GEODE-5103: When applying transactional update on a replicate, callbacks should be alwasy generated.
Currently callbacks is not generated if a region entry is null possibly caused by rebalance etc.
We still want the node to generate callbacks for its clients.
> During rebalance, a client node may miss a transactional event
> --------------------------------------------------------------
>
> Key: GEODE-5103
> URL: https://issues.apache.org/jira/browse/GEODE-5103
> Project: Geode
> Issue Type: Bug
> Components: transactions
> Reporter: Eric Shu
> Assignee: Eric Shu
> Priority: Major
>
> During rebalance, a new primary bucket could be created on another node while the original primary bucket become secondary in a short period of time. If a transaction occurs on the primary bucket node, TXCommitMessage will be sent to the secondary primary bucket node.
> There is a race that a event could be missed to be added to the subscription queue when the now secondary bucket is being removed to satisfy the redundancy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)