[wildfly-dev] WFLY-818 Slave host does not register to DC

[Brian Stansberry]

On 1/22/14, 8:49 AM, Claudio Miranda wrote:
> Hi
>
> On Wed, Jan 22, 2014 at 9:58 AM, Emanuel Muckenhuber
> <emuckenh at redhat.com> wrote:
>> There are other open issues related to
>> this, i.e. when using --cached-dc and --backup-dc at the same time.
>
> What do you think to let this as default ?
> Thinking from a HA view, the sysadmin, always wants their HC to work,
> so, if HC caches a local copy by default, it makes sense to load it if
> HC cannot registers itself with DC.
>
> I have worked with some customers, they just want to start jboss,
> regardless if HC are able to connect to DC. Of course, there should
> exist some mechanism to warn sysadmin the registration was not
> possible and they must look into it.
>

If we made --cached-dc + --backup-dc semantics the default, we'd have to 
introduce some mechanism to turn them off. I'm not sure the gain is 
worth it, particularly in the --cached-dc case. If you're starting an HC 
I think it's better to explicitly state that you're ok with that HC 
being out of sync with the domain.

OTOH, --backup-dc by default makes a lot of sense. If we don't have a 
local copy of the domain config and then the admin discovers he needs 
one so he can start the HC, it's too late.



-- 
Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat