[jboss-jira] [JBoss JIRA] (WFLY-2917) Unhelpful logging related to slave HC failover

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry reassigned WFLY-2917:
--------------------------------------

    Assignee: Brian Stansberry

    
> Unhelpful logging related to slave HC failover
> ----------------------------------------------
>
>                 Key: WFLY-2917
>                 URL: https://issues.jboss.org/browse/WFLY-2917
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>    Affects Versions: 8.0.0.Final
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: 8.0.1.Final
>
>
> In 8.0.0 we introduced the "discovery-options" notion to the HC's domain-controller config. One expected usage pattern is there will be a master HC and then one or more slaves started with --backup-dc that act as passive failover DC's. Other slaves will use discovery-options elements to configure all possible masters. If the regular master fails, a backup can be quickly converted to a master with a couple CLI ops.
> This works, except the slave shows some unhelpful logging while waiting for the backup to be promoted:
> {code}
> [Host Controller] 14:58:13,105 WARN  [org.jboss.as.host.controller] (Remoting "besdev:MANAGEMENT" task-3) JBAS010914: Connection to remote host-controller closed. Trying to reconnect.
> [Host Controller] 14:58:13,134 INFO  [org.jboss.as.host.controller] (domain-connection-threads - 1) JBAS010916: Reconnected to master
> [Host Controller] 14:58:14,160 INFO  [org.jboss.as.host.controller] (domain-connection-threads - 1) JBAS010916: Reconnected to master
> [Host Controller] 14:58:18,180 INFO  [org.jboss.as.host.controller] (domain-connection-threads - 1) JBAS010916: Reconnected to master
> [Host Controller] 14:58:27,200 INFO  [org.jboss.as.host.controller] (domain-connection-threads - 1) JBAS010916: Reconnected to master
> [Host Controller] 14:58:42,216 INFO  [org.jboss.as.host.controller] (domain-connection-threads - 1) JBAS010916: Reconnected to master
> [Host Controller] 14:58:57,232 INFO  [org.jboss.as.host.controller] (domain-connection-threads - 1) JBAS010916: Reconnected to master
> [Host Controller] 14:59:12,248 INFO  [org.jboss.as.host.controller] (domain-connection-threads - 1) JBAS010916: Reconnected to master
> [Host Controller] 14:59:27,264 INFO  [org.jboss.as.host.controller] (domain-connection-threads - 1) JBAS010916: Reconnected to master
> [Host Controller] 14:59:42,280 INFO  [org.jboss.as.host.controller] (domain-connection-threads - 1) JBAS010916: Reconnected to master
> [Host Controller] 14:59:57,296 INFO  [org.jboss.as.host.controller] (domain-connection-threads - 1) JBAS010916: Reconnected to master
> [Host Controller] 15:00:12,312 INFO  [org.jboss.as.host.controller] (domain-connection-threads - 1) JBAS010916: Reconnected to master
> [Host Controller] 15:00:27,328 INFO  [org.jboss.as.host.controller] (domain-connection-threads - 1) JBAS010916: Reconnected to master
> [Host Controller] 15:00:42,351 INFO  [org.jboss.as.host.controller] (domain-connection-threads - 1) JBAS010916: Reconnected to master
> {code}
> What's happening there is the slave is connecting to the backup but is not being allowed to register as a slave because the backup is not yet a master. The logging should reflect what's actually happening.
> Also, after the backup is promoted and the slave properly registers, there's nothing in the slaves logs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira