[jboss-jira] [JBoss JIRA] (WFLY-818) Slave host does not register to DC when starting with --cached-dc and DC is available
[
https://issues.jboss.org/browse/WFLY-818?page=com.atlassian.jira.plugin.s...
]
Jaromir Hamala commented on WFLY-818:
-------------------------------------
I'm afraid that this issue effectively makes DC to be a Single Point of Failure. You
have these options:
1. starting the HC with --cached-dc, but it effectively downgrades it to a standalone mode
as is never attempts to contact DC
2. do not use the --cached-dc, but than you HC will fail to start if DC is not available
Given there is no guide how to make DC highly available, it's a very unfortunate
situation and possible a showstopper for deploying JBoss.
Slave host does not register to DC when starting with --cached-dc and
DC is available
-------------------------------------------------------------------------------------
Key: WFLY-818
URL: https://issues.jboss.org/browse/WFLY-818
Project: WildFly
Issue Type: Bug
Components: Domain Management
Reporter: Manel Martinez Gonzalez
NOTE: this is related to AS7-4281 (see
https://issues.jboss.org/browse/AS7-4281?focusedCommentId=12682058&pa...
)
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
--
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