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

Singleton deployment not stopped on the previous singleton provider after new provider is elected

    XMLWordPrintable

Details

    • Hide

      Can be reproduced locally:
      1. extract two instances of EAP 7.1.0.DR11, modify standalone-ha.xml (see Description)
      2. add a singleton deployment
      3. start the first server with standalone-ha configuration, wait until it started, and then start the second one
      4. second node must be elected as a new singleton provider, if not, you can start some other nodes
      5. there will be 2 servers with the singleton deployment deployed

      Show
      Can be reproduced locally: 1. extract two instances of EAP 7.1.0.DR11, modify standalone-ha.xml (see Description) 2. add a singleton deployment 3. start the first server with standalone-ha configuration, wait until it started, and then start the second one 4. second node must be elected as a new singleton provider, if not, you can start some other nodes 5. there will be 2 servers with the singleton deployment deployed

    Description

      Scenario: failover clustering test with singleton deployment.

      Singleton subsystem configuration
      <subsystem xmlns="urn:jboss:domain:singleton:1.0">
        <singleton-policies default="default">
          <singleton-policy name="default" cache-container="server">
            <random-election-policy/>
          </singleton-policy>
        </singleton-policies>
      </subsystem>
      

      Nodes startup order: node1, node2, node3, node4.
      During node1 startup, this server is elected as the singleton provider and deploys singleton deployment. During other servers startup, some other node (usually node2) is elected as the singleton provider and deploys singleton deployment. However, node1 has the singleton deployment still deployed, so there are 2 nodes effectively providing a singleton deployment.

      Deployment used: clusterbench-ee7-singleton-jbossall.ear
      Standard clusterbench application with modified jboss-all.xml:

      <?xml version="1.0" encoding="UTF-8"?>
      <jboss xmlns="urn:jboss:1.0">
          <singleton-deployment xmlns="urn:jboss:singleton-deployment:1.0"/>
      </jboss>
      

      Server log:
      http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-singleton-deployment-jvmkill-random-election-policy/7/console-perf18/

      Attachments

        Issue Links

          Activity

            People

              rhn-engineering-rhusar Radoslav Husar
              rhn-engineering-rhusar Radoslav Husar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: