Bug 1271898 – Changes while one node is down are not replicated after the node reboot

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1271898 - Changes while one node is down are not replicated after the node reboot

Summary:	Changes while one node is down are not replicated after the node reboot

Status:	VERIFIED

Aliases:	None

Product:	JBoss BRMS Platform 6
Classification:	Retired
Component:	Business Central (Show other bugs)
Sub Component:
Version:	6.1.0
Hardware:	Unspecified Unspecified

Priority	urgent Severity high
Target Milestone:	CR2
Target Release:	6.2.0
Assigned To:	Alexandre Porcelli
QA Contact:	Radovan Synek
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1283953
Blocks:	1273649
	Show dependency tree / graph

Reported:	2015-10-14 22:33 EDT by Toshiya Kobayashi
Modified:	2015-12-21 11:15 EST (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	When setting up a cluster with Apache Zookeeper/Helix, changes to node 1 while node 2 is offline are not reduplicated to node 2. This is caused by incorrect settings of org.uberfire.cluster.autostart. To work around the issue, make sure the org.uberfire.cluster.autostart is set to false by adding a following line to the host.xml domain configuration file: <property name="org.uberfire.cluster.autostart" value="false" boot-time="false"/>
Story Points:	---
Clone Of:
Clones:	1273649 (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:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Toshiya Kobayashi 2015-10-14 22:33:12 EDT

Description of problem:

Set up BRMS 6.1.0 cluster with Helix/ZooKeeper following the document (https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BRMS/6.1/html/Installation_Guide/chap-Clustering.html).

Changes made by node1 (e.g. creating a repo) while node2 is down, are not replicated to node2 even after node2 restart.

Steps to Reproduce:
1. Start a cluster (node1/node2)
2. Make changes in node1 via business-central
 - Create a repo
 - Create a guided rule
 - Edit a guided rule
3. Confirm that the changes are replicated to node2
4. Shutdown node2
5. Make changes in node1 again
 - Create a repo
 - Create a guided rule
 - Edit a guided rule
6. Start node2

Actual results:

The changes in step 5 are not replicated to node2

Expected results:

The changes in step 5 are replicated to node2

Comment 2 Toshiya Kobayashi 2015-10-22 22:20:13 EDT

This is a document bug so I filed BZ1274569.

There was no code fix needed but I'm not closing this BZ so that this scenario will be covered by QA test.

Comment 3 Radovan Synek 2015-11-20 06:32:27 EST

Cannot be verified due to bug 1283953

Comment 4 Radovan Synek 2015-12-01 08:21:38 EST

Verified with BPMS-6.2.0.CR2

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