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

Former singleton provider node leaving cluster after re-election causes another re-election

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 7.1.0.DR17
    • 7.1.0.DR15
    • Clustering
    • None

      With a random election policy, this situation is likely to happen:
      1. After a topology change, new singleton provider is elected
      2. Former singleton provider undeploys the singleton application, which causes it to leave a cluster for a while
      3. This topology change triggers another election
      4. Loop continues

            pferraro@redhat.com Paul Ferraro
            mvinkler1@redhat.com Michal Vinkler
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: