Hi, > two cluster nodes working for a while. > 100000 revisions in the datastore. > add a third cluster node > it's replaying 100000 journal entries > Is there a way of having the third (new) cluster node start at the latest > Global-Revision immediately?
There seems to be a related feature: https://issues.apache.org/jira/browse/JCR-1087 - I'm not sure if this will solve the problem however (I don't really know this feature) > If I temporarily shut down the second cluster node I receive the following > error messages during synchronization at restarting this second node: I am not sure, it sounds like a bug... Could you create a Jira issue for this, together with a simple reproducible test case? Regards, Thomas
