Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-4618

ClusterTopologyManagerImpl join during cluster status recovery


    • EAP 7.0.1

      If the joiner has the correct view id, but the current status is
      RECOVERING_CLUSTER, we should wait for the cluster status recovery to
      finish before adding the new member.

      We are currently not doing that, so the new member could be erased by the status recovery process that's in progress. This can happen if the coordinator joiner already had been a member of the JGroups cluster for some time, and there's no view change when they actually start their caches (exactly the scenario in ConcurrentStartTest).

            dberinde@redhat.com Dan Berindei (Inactive)
            rhn-support-bmaxwell Brad Maxwell
            0 Vote for this issue
            2 Start watching this issue