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

deployed applications are not distributed to host controller(s)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 8.1.0.CR2
    • Fix Version/s: 9.0.0.Alpha1
    • Component/s: Management
    • Labels:
      None
    • Environment:

      Wildfly 8.1.0 CR5 domain mode

    • Steps to Reproduce:
      Hide
      • Install node 1 using wildfly 8.1.0 CR5
      • remove all local servers
      • start it in domain mode, so it runs as the DC
      • use the CLI to deploy an application

      => the application will end up in the domain/data/content folder as expected.

      • Install node 2 on another machine
      • remove all local servers
      • point it to the DC on node 1
      • start in domain mode, so it runs as a HC
      • wait a little...
      • stop the node 2, and inspect the local domain/data/content
        => empty
      • start node 2 again
      • on node 1, with the CLI, deploy a second application
      • inspect node 2 local domain/data/content
        => the new / 2nd application will have been copied but the original first is still not copied.

      Whether you start node 2 with or without "--backup" makes no difference.

      Problem:
      due to the HC not receiving a full copy of the "content" folder, it is not possible to promote the HC to a DC (when the original DC is down)

      Show
      Install node 1 using wildfly 8.1.0 CR5 remove all local servers start it in domain mode, so it runs as the DC use the CLI to deploy an application => the application will end up in the domain/data/content folder as expected. Install node 2 on another machine remove all local servers point it to the DC on node 1 start in domain mode, so it runs as a HC wait a little... stop the node 2, and inspect the local domain/data/content => empty start node 2 again on node 1, with the CLI, deploy a second application inspect node 2 local domain/data/content => the new / 2nd application will have been copied but the original first is still not copied. Whether you start node 2 with or without "--backup" makes no difference. Problem: due to the HC not receiving a full copy of the "content" folder, it is not possible to promote the HC to a DC (when the original DC is down)
    • Workaround Description:
      Hide

      Do not promote an HC. Instead have a backup of the DC and restore when needed.

      Show
      Do not promote an HC. Instead have a backup of the DC and restore when needed.
    • Bugzilla Update:
      Perform

      Description

      when a new HC is brought up into an existing DC/HC environment, it does not receive a copy of all deployed applications (e.g. the "content" folder)

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                brian.stansberry Brian Stansberry
                Reporter:
                tfonteyn Tom Fonteyne
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: