You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Vadim Lotarev (JIRA)" <ji...@apache.org> on 2018/02/27 09:45:00 UTC
[jira] [Created] (GEODE-4748) Geode transaction is not consistent
in case of networking problems
Vadim Lotarev created GEODE-4748:
------------------------------------
Summary: Geode transaction is not consistent in case of networking problems
Key: GEODE-4748
URL: https://issues.apache.org/jira/browse/GEODE-4748
Project: Geode
Issue Type: Bug
Components: transactions
Reporter: Vadim Lotarev
Geode cache became inconsistent in case if networking problems occur at commit time. How to reproduce:
# create any simple _replicated_ region
# run two nodes
# put some value in the region within a transaction
# execute query on both nodes to check that the same value is returned (I used JMX for that)
# emulate somehow temporary networking error (I changed the code throwing IOException from toData())
# repeat [#3], exception should occur
# repeat [#4] - you should see different values on different nodes
It looks like errors occurred after {{TXState.applyChanges}} produce inconsistency - it is impossible to rollback applied local changes what leads to the state where local cache contains changed data but other node(s) old data (before changes made in transaction).
To me, consistency is a key property for the systems like Geode so I would consider this bug as a critical one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)