Bug 1161214 - Split brain: inconsistent data after merge
Summary: Split brain: inconsistent data after merge
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ER7
: 6.4.0
Assignee: Dan Berindei
QA Contact: Martin Gencur
Depends On:
Blocks: 1165095
TreeView+ depends on / blocked
Reported: 2014-11-06 16:18 UTC by Radim Vansa
Modified: 2015-01-28 13:29 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
In Red Hat JBoss Data Grid, when the cluster splits into multiple parts (usually due to networking issues such as a crashed router between two sites), JBoss Data Grid can detect this situation and reduce availability (prohibit reads or writes) to keep the data consistent until the cluster is re-connected. If a write to the cache is issued soon after the cluster split is detected, this update may be lost or different nodes may read different versions of the entry. This is a known issue in JBoss Data Grid 6.4 Beta and the workaround for this issue is to avoid updating the cache contents before the cluster topology stabilizes.
Clone Of:
: 1165095 (view as bug list)
Last Closed:
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-4949 0 Critical Resolved Split brain: inconsistent data after merge 2015-05-04 08:01:29 UTC
Red Hat Issue Tracker ISPN-5030 0 Minor Resolved NPE during node rebalance after a leave 2015-05-04 08:01:29 UTC

Description Radim Vansa 2014-11-06 16:18:40 UTC

Comment 5 Radim Vansa 2014-11-18 08:37:28 UTC
Misha, Divya was commenting using paragraph from docs, not BZ.

The current info in BZ is sufficient, just make sure that docs are in sync with this BZ.

Comment 7 Radim Vansa 2014-12-11 13:20:48 UTC
It seems that my test has passed the situation where it was occuring, therefore closing this bug (further testing has trouble due to ISPN-5000 tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1166243)

Note You need to log in before you can comment on or make changes to this bug.