Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-4946 Upgrade JGroups to 2.6.19
  3. JBPAPP-5900

Race condition in FLUSH when master leaves cluster

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.1.1
    • EAP_EWP 5.1.0
    • Clustering
    • None
    • Release Notes
    • Hide
      A race condition in the JGroups FLUSH protocol caused messages to be processed in the wrong order when the master node left the cluster, so the master node left before sending a new view (with a new master). Therefore, the other nodes did not detect the master's absence, or elect a new master, until the master's absence was detected by the failure detection protocol.
      This was fixed, and the race condition no longer occurs.
      Show
      A race condition in the JGroups FLUSH protocol caused messages to be processed in the wrong order when the master node left the cluster, so the master node left before sending a new view (with a new master). Therefore, the other nodes did not detect the master's absence, or elect a new master, until the master's absence was detected by the failure detection protocol. This was fixed, and the race condition no longer occurs.
    • Documented as Resolved Issue

      There's a race condition in FLUSH when the master node is leaving the cluster,
      that can cause the master to not send a new view (with a new master) before leaving.

              ozizka_jira Ondrej Zizka (Inactive)
              rhn-support-dereed Dennis Reed
              Laura Bailey Laura Bailey
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: