Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1271898

Summary: Changes while one node is down are not replicated after the node reboot
Product: [Retired] JBoss BRMS Platform 6 Reporter: Toshiya Kobayashi <tkobayas>
Component: Business CentralAssignee: Alexandre Porcelli <porcelli>
Status: CLOSED EOL QA Contact: Radovan Synek <rsynek>
Severity: high Docs Contact:
Priority: urgent    
Version: 6.1.0CC: eignatow, kverlaen, mczernek
Target Milestone: CR2   
Target Release: 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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:
: 1273649 (view as bug list) Environment:
Last Closed: 2020-03-27 19:05:05 UTC 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: 1283953    
Bug Blocks: 1273649    

Description Toshiya Kobayashi 2015-10-15 02:33:12 UTC 
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-23 02:20:13 UTC 
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 11:32:27 UTC 
Cannot be verified due to bug 1283953
Comment 4 Radovan Synek 2015-12-01 13:21:38 UTC 
Verified with BPMS-6.2.0.CR2