[
https://issues.apache.org/jira/browse/GEODE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16639047#comment-16639047
]
ASF subversion and git services commented on GEODE-5828:
--------------------------------------------------------
Commit 33ce8ad4c0b5808d2f0371297df901aab6a79d7e in geode's branch
refs/heads/feature/GEODE-5828 from eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=33ce8ad ]
GEODE-5828: fixes replicates miss transaction commit.
* Always send CommitProcessQueryMessage to other replicates to see if anyone
received second message
as transaction originator for client transaction will be different from
transation host.
* Do not wait for transaction originator to depart when transaction host is
crashed. Originator may
not be the same as the crashed transaction host and never departs from
distributed system.
> A replicate does not apply transaction commit even if another replicate
> applied commit after tx host departed
> -------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-5828
> URL: https://issues.apache.org/jira/browse/GEODE-5828
> Project: Geode
> Issue Type: Bug
> Components: transactions
> Affects Versions: 1.1.0
> Reporter: Eric Shu
> Assignee: Eric Shu
> Priority: Major
>
> A transaction commit is done by sending two messages to all replicates by the
> transaction host. If host crashes when it is sending the second message to
> replicates, there is a possibility that some replicates receive it and others
> do not.
> The replicates missed second message will send query to all replicates to see
> if any one received the second message. If so, it will commit as well.
> However, there is a bug, in some cases that the query is not even sent and
> cause this replicate missed commit -- thus causes the data inconsistency
> among the replicates.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
