Thank you Nicklas,
But I have notice that when the domain controller goes offline, after some time, the host-controller of the slave node shutdowns everything including the servers and himself. So perhaps the only thing I would need, is not another domain controller, but to avoid this undesired sided effect. Is there a way to avoid this?
I guess one problem would be that when the original master would come back online, the old one and the new one would have to play paper-rock-scissors over which should back down.
Ok, but if we forget the point about having more than one domain controller and you look at the link you posted before, the first point:
"1) Servers don't need a running domain controller in order to handle
Is simply don't working to me because the servers shutdown.
Answering to your last post in the case when two node becames master there well are defined algorithms to solve that. Paper-rock-scissors could be one option, other, simplest to me, could be to say somewhere which node have priority to other in order to became muster. Red Hat cluster failover domains work in this way.
I've configured the Wildfly HA configuration using Domain controller with Mod-cluster in AWS VPC, but here in this config has a single point of failure, if the domain controller is down all the hosts will be down. Is there anyway to configure Domain controller in HA(two domain controller shares the session data) mode?
Thanks in advance!
If the domain controller crash, neither the host-contollers nor the servers are affected if the DC is a separate instance.
You can restart the DC and the slave hosts should able to re-connect.
BTW you should open a new thread as this is an old thread and also a different question