[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1173) Merge after lost of network connectivity between cluster members (handle the split-brain situation)
Tim Fox (JIRA)
jira-events at lists.jboss.org
Fri Feb 6 02:20:44 EST 2009
[ https://jira.jboss.org/jira/browse/JBMESSAGING-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Fox closed JBMESSAGING-1173.
--------------------------------
Resolution: Out of Date
1194 is handling split brain.
With JBM 2.0 we shouldn't need to merge since we should prevent split brain from happening in the first place (using a quorum)
> Merge after lost of network connectivity between cluster members (handle the split-brain situation)
> ---------------------------------------------------------------------------------------------------
>
> Key: JBMESSAGING-1173
> URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1173
> Project: JBoss Messaging
> Issue Type: Feature Request
> Components: JMS Clustering
> Affects Versions: 1.4.0.SP2
> Environment: Any clustered
> Reporter: Mike Clark
> Assignee: Tim Fox
> Fix For: 2.0.0 Beta
>
>
> JBM does not currently support the merging of cluster segments that have gotten into the "split-brain" situation. This occurs when network connectivity is lost between subsets of a cluster. Each subset assumes the other is gone and acts appropriately. When the network connectivity is restored, they do not merge back into a single cluster but remain as independent clusters (the spit-brain).
> This feature request is to add cluster merging to prevent the split-brain situation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list