Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-316

Slave host does not register to DC when starting with --cached-dc and DC is available

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 3.0.0.Alpha4
    • None
    • Management
    • None

    Description

      NOTE: this is related to AS7-4281 (see https://issues.jboss.org/browse/AS7-4281?focusedCommentId=12682058&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12682058 )

      When a slave host is started with --cached-dc option it won't register to Domain Controller although it's available. domain.sh help says "If this host is not the Domain Controller and cannot contact the Domain Controller at boot, boot using a locally cached copy of the domain configuration (see --backup)" and this is not really happening because slave host never contact to DC with --cached-dc

      Attachments

        Issue Links

          is cloned by

          Feature Request - Feature requests from customers and/or users WFCORE-324 Resolve startup dependency between master hostController and slave hostControllers.

          • 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 related to

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-317 Failed to start server when -backup -cached-dc are used together

          • 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
          relates to

          Feature Request - Feature requests from customers and/or users WFCORE-338 Auto-promotion of slave HC to master

          • 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.
          • Coding In Progress

          Bug - A problem that impairs or prevents the functions of the product. AS7-4413 Addressing the shutdown command to an unknown host results in shutdown of the Domain Controller

          • 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.
          • Resolved

          Activity

            People

              kwills@redhat.com Ken Wills
              mmartinez-gonzalez Manel Martinez Gonzalez (Inactive)
              Votes:
              14 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: