-
1. Re: domain controller - single point of failure?
emuckenhuber Dec 12, 2012 10:08 AM (in response to lloydfischer)Lloyd Fischer wrote:
So is non-ha domain mode really dependent on the domain controller for the operation of any server? If so, this is not really production ready. I must be missing something.
It is obviously required to get the initial configuration model and for the manageability, however not required for the operation of the actual servers.
-
2. Re: domain controller - single point of failure?
emuckenhuber Dec 12, 2012 10:09 AM (in response to lloydfischer)Lloyd Fischer wrote:
I see references to command line options --backup and --cached-dc that should allow the server to start without a DC, but bug https://issues.jboss.org/browse/AS7-4281 wold indicate this doesn't work.
You can use either of those. You can either use --backup to keep a local copy of the domain model. If the domain-controller is down and you shutdown the slave host you would need to use the --cached-dc to start the local slave host-controller using the backed-up model.
-
3. Re: domain controller - single point of failure?
lloydfischer Dec 12, 2012 10:24 AM (in response to emuckenhuber)If I understand, in production I would need two operation modes. Normal mode will start up with --backup. In an emergency if the domain controller is unavailable I would need to startup the slave hosts with --cached-dc. Then when the DC is restored I would have to restart the slave hosts in --backup.
I may not understand all the details, but since the slave host knows whether the DC is available or not it would seem capable of choosing the mode itself.
-
4. Re: domain controller - single point of failure?
lloydfischer Dec 12, 2012 10:35 AM (in response to lloydfischer)https://issues.jboss.org/browse/AS7-4412 is about this issue. When --cached-dc is specified, the DC is not contacted at all.
-
5. Re: domain controller - single point of failure?
emuckenhuber Dec 12, 2012 10:50 AM (in response to lloydfischer)1 of 1 people found this helpfulYes, that sounds about right. --backup tells the host-controller to backup the model locally. --cached-dc to not connect to the remote domain-controller and use the locally cached model instead.
I am really just stating what it does at the moment. I haven't really looked into how much work would be required to have a combined mode, donig what you described that automatically.