[
https://issues.apache.org/jira/browse/GEODE-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450255#comment-16450255
]
ASF subversion and git services commented on GEODE-5103:
--------------------------------------------------------
Commit 4a385b8ac4d7c1f6db6fc12c35e80871c7a1edbe in geode's branch
refs/heads/develop from [~eshu]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4a385b8 ]
GEODE-5103: When applying transactional update on a replicate, callba… (#1825)
* GEODE-5103: When applying transactional update on a replicate, callbacks
should be always 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
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> 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)
