Bug 1090907
| Summary: | Cluster sync on startup is not working | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Pedro Zapata <pzapataf> | ||||
| Component: | Business Central | Assignee: | Maciej Swiderski <mswiders> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Jiri Locker <jlocker> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.0.1 | CC: | kverlaen, lpetrovi, rrajasek | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-08-27 05:42:11 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: | |||||||
| Attachments: |
|
||||||
|
Description
Pedro Zapata
2014-04-24 11:38:43 UTC
Pedro, org.uberfire.cluster.autostart property must be set to false in clustered environment to avoid duplicated writes on cluster startup. The main issue here is that when there is something cloned on application start - like we take repositories from github for community both servers will clone the repositories and then (if cluster is auto started) start broadcasting clone repo events causing other cluster members to receive and re-clone repositories. That is undesired behavior and thus this auto start is disabled unless application is completely configured and running. Even if the same fix for URI would be applied it will cause issues described above and thus auto start must always be disabled for clustered setups. Does that make sense to you? Maciej, Thanks for the clarification, however this raises a question. How a newly created node will get in sync with the rest of the cluster's repositories? Is there a mechanism for this? Or is it assumed that all cluster's node will start from the same state? Pedro, this is responsibility of helix and zookeeper to provide all sync information to the servers that join the cluster. It has be discovered not working properly and fixed as part of this bz https://bugzilla.redhat.com/show_bug.cgi?id=1100097 so once it gets verified by QA we should be good on this. I believe this can be closed as BZ 1100097 has been implemented and verified so this one is duplicate *** This bug has been marked as a duplicate of bug 1100097 *** |