Hi, we don't have a solution yet. There are other open issues related to this, i.e. when using --cached-dc and --backup-dc at the same time. We do plan on allowing this case in future, which should behave similar to what you described. However it will probably only happen in the WidlFly 9 time frame. Emanuel On 01/22/2014 04:09 AM, Claudio Miranda wrote: > Hi, do you have any solution for this ? > > What do you think about this ? > > 1. HC starts with NO --cached-dc, it try to registers to DC, if it > doesn't register, HC fails to starts, as it is today. > > 2. HC starts with --cached-dc, it try to registers to DC, > a) if HC doesn't register to DC, HC uses the cached copy of > domain.xml. Try to registers to DC at interval times, if register is > successful see 3.a > b) if HC registers to DC, it works as is today copy domain.xml from DC > and replaces local backup. > > 3. HC starts with NO --cached-dc, HC register to DC, everything works > as is today. If HC disconnects from DC (unknown reason), HC keeps > trying to registers at interval times. > a) HC re-connects to DC, and detects domain.xml changed between DC and > HC. HC emits a warning and asks to restart the HC and their servers. > > > regards > _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

Hi On Wed, Jan 22, 2014 at 9:58 AM, Emanuel Muckenhuber <emuckenh(a)redhat.com&gt; 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.