Thanks JB. I'll just have to take a look at the code at some point to fully understand it. I'll check it out after you do the release for 2.2.5.
Is there any way to "queue" multiple changes so they all take place at once? That is probably closer to the Fuse Fabric profile concept though. Thanks, Chris On Wed, Nov 21, 2012 at 9:50 AM, Jean-Baptiste Onofré <[email protected]>wrote: > Hi Chris, > > In Cellar, you have the Synchronizers that pull/push the configuration > (and the others resources). > > You have two cases: > > 1/ when a new node join a cluster group, the synchronizer is called > 2/ if a node leaves Cellar (for instance, network issue) and get > "outdated" regarding the distributed configuration and resources states, > you have to refresh cellar to call the synchronizer again > > For 2/, I plan to add a cluster:sync command (and the corresponding MBean) > to "force" the call to the synchronizer. > It will be included in Cellar 2.2.5 (that I plan to release tonight ;)). > > Regards > JB > > > On 11/21/2012 05:41 PM, Chris Geer wrote: > >> I've been looking at Karaf Cellar and have a question regarding >> configuration changes and offline containers. My understanding is that >> configuration changes are propagated amongst the containers through the >> Hazelcast topics/queue. Is there anything in place to handle the case >> where one container was offline/disconnected from the Hazelcast cluster >> during a config change to re-sync once it connects again? >> >> Thanks, >> Chris >> > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
