Bug 1161214
| Summary: | Split brain: inconsistent data after merge | |||
|---|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Radim Vansa <rvansa> | |
| Component: | Infinispan | Assignee: | Dan Berindei <dberinde> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Gencur <mgencur> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 6.4.0 | CC: | dmehra, dstahl, gsheldon, jdg-bugs, mhusnain, rvansa | |
| Target Milestone: | ER7 | |||
| Target Release: | 6.4.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| 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.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1165095 (view as bug list) | Environment: | ||
| Last Closed: | Type: | Bug | ||
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1165095 | |||
|
Description
Radim Vansa
2014-11-06 16:18:40 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. 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) |