You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Eric Shu (JIRA)" <ji...@apache.org> on 2018/10/04 18:52:00 UTC
[jira] [Created] (GEODE-5828) A replicate does not apply
transaction commit even if another replicate applied commit after tx host
departed
Eric Shu created GEODE-5828:
-------------------------------
Summary: 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
Reporter: Eric Shu
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)