[jboss-jira] [JBoss JIRA] (WFCORE-1882) Deal with WFCORE-1052 functionality in the HA DC case
Ken Wills (JIRA)
issues at jboss.org
Mon Nov 21 19:34:00 EST 2016
[ https://issues.jboss.org/browse/WFCORE-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13326002#comment-13326002 ]
Ken Wills commented on WFCORE-1882:
-----------------------------------
This was completed here: https://github.com/bstansberry/wildfly-core/commit/e496bee63851ed53811fbbb83cbad978b867b536
> Deal with WFCORE-1052 functionality in the HA DC case
> -----------------------------------------------------
>
> Key: WFCORE-1882
> URL: https://issues.jboss.org/browse/WFCORE-1882
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Ken Wills
>
> WFCORE-1052 adds the ability to reload a process to a different config file from what it is currently running. That includes the domain-wide config file if the reloading process is a master HC.
> I don't think we want to support this in a WFCORE-338 scenario, as it amounts to a mechanism to force a different domain-wide config into the domain. I think we should have a more specific, controlled mechanism for that.
> Once WFCORE-1881 is implemented HostProcessReloadHandler can check LocalHostControllerInfo to see if its running in a CDC. Note that this issue may have implications on the design of WFCORE-1881. That is, it may not be the case that if LHCI.isMaster() is true then LHCI.isCandidateDomainController() is true. Perhaps an HC configured in the EAP 7.0 and earlier style could be a master but not a CDC. For such an HC the WFCORE-1052 functionality could be available.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list