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

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.1.0.DR17
    • 7.1.0.DR15
    • Clustering
    • 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

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10677 Singleton deployment functionality completely broken

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-8540 Former singleton provider node leaving cluster after re-election causes another re-election

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: