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

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

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 11.0.0.Alpha1
    • Fix Version/s: 11.0.0.Beta1
    • Component/s: Clustering
    • Labels:
      None

      Description

      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

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  pferraro Paul Ferraro
                  Reporter:
                  pferraro Paul Ferraro
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: