Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-8540

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 11.0.0.Beta1
    • 11.0.0.Alpha1
    • 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
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: