• Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.3.0.ER1
    • EAP_EWP 5.2.0
    • Clustering
    • None
    • Release Notes
    • Hide
      Previous versions of JBoss EAP 5 had a race condition that manifested in some instances of a new node joining a cluster. The race was encountered when a Master node initiated a flush of existing cluster members upon receipt of a join request and then allowed the new node to join the cluster. The new node would then initiate a flush before transferring the initial cluster state. But in some circumstances it could process the stop flush message from the previous flush by the master and return prematurely.

      Fix: When starting a flush while joining the cluster, any previously received stop_flush notifications are now discarded.
      Show
      Previous versions of JBoss EAP 5 had a race condition that manifested in some instances of a new node joining a cluster. The race was encountered when a Master node initiated a flush of existing cluster members upon receipt of a join request and then allowed the new node to join the cluster. The new node would then initiate a flush before transferring the initial cluster state. But in some circumstances it could process the stop flush message from the previous flush by the master and return prematurely. Fix: When starting a flush while joining the cluster, any previously received stop_flush notifications are now discarded.
    • Needs More Info
    • NEW

      There is a race condition in STOP_FLUSH when a node joins the cluster and initiates state transfer.

      This can prevent the node from joining successfully.

            rhn-support-dereed Dennis Reed
            rhn-support-dereed Dennis Reed
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: