Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-6020

SynchServerOperation pulls down more config than necessary during slave reconnection to DC

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.0.DR6
    • None
    • Management
    • None
    • Hide
      1. start DC
        ./jboss-eap-7.1/bin/domain.sh --host-config=host-master.xml
      2. start slave with --cached-dc
        ./jboss-eap-7.1/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=19999 --cached-dc
      3. stop slave
      4. open jboss-eap-7.1/domain/configuration/domain.cached-remote.xml

      it contains empty profile elements

      <profiles>
    <profile name="full-ha"/>
    <profile name="full"/>
</profiles>
      Show
      start DC ./jboss-eap-7.1/bin/domain.sh --host-config=host-master.xml start slave with --cached-dc ./jboss-eap-7.1/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=19999 --cached-dc stop slave open jboss-eap-7.1/domain/configuration/domain.cached-remote.xml it contains empty profile elements <profiles> <profile name= "full-ha" /> <profile name= "full" /> </profiles>

    Description

      When a slave disconnects and reconnects to the DC for the first time, a complete copy of the domain config is sent. If the slave is using the default ignore-unused-configuration semantics, it still adds all of the additional configuration.

      An additional side issue is the full-ha subsystems are being added in reverse order.

      More detail in comments here https://github.com/wildfly/wildfly-core/pull/1754.

      Attachments

        Issue Links

          clones

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFCORE-1773 SynchServerOperation pulls down more config than necessary during slave reconnection to DC

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-6068 (7.1.0) Upgrade to WildFly Core 3.0.0.Alpha9

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              kwills@redhat.com Ken Wills
              msimka@redhat.com Martin Simka
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: