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

HA Singleton will not stop the service or deployment after merge the cluster-view if the elected node rejected by FullGC or suspended

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Critical Critical
    • None
    • 16.0.0.Beta1
    • Clustering
    • None
    • Hide

      User ha-singleton-deployment or ha-singelton-service quickstarts
      start two nodes
      deploy the application for both
      -> one node is elected and run the singleton
      stop the node running the singleton by suspend (Ctrl-Z)
      -> backup will start the singeton
      resume the first node
      -> both nodes will process the singleton

      Show
      User ha-singleton-deployment or ha-singelton-service quickstarts start two nodes deploy the application for both -> one node is elected and run the singleton stop the node running the singleton by suspend (Ctrl-Z) -> backup will start the singeton resume the first node -> both nodes will process the singleton

      If a 2 node cluster has a HA Singleton deployment (no matter whether it is a service or deployment) a merge after a split caused by FullGC will end in running two nodes as a Singleton provider.

        1. node1.log
          70 kB
          Wolf Fink
        2. node2.log
          27 kB
          Wolf Fink

            pferraro@redhat.com Paul Ferraro
            rhn-support-wfink Wolf Fink
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: