You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by Adrien Lamoureux <la...@gmail.com> on 2014/10/25 23:41:16 UTC
clustering and synchronization
Hello,
What kind of delay is expected between cluster nodes when a change is made
in one oak instance, and another oak instance needs to become aware of that
change?
How stable is clustering is Oak?
I currently have 2 instances of Oak 1.0.7, both using a single instance of
MongoDB 2.6.4, all running on the same system (locally)
I deleted a node, and 30 seconds later or so, I made a change triggering an
event that the other instance is listening for, but I get this:
----------------------------------------------------------
----------------------------------------------------------
javax.jcr.InvalidItemStateException: This item does not exist anymore
at
org.apache.jackrabbit.oak.jcr.delegate.ItemDelegate.checkAlive(ItemDelegate.java:85)
at
org.apache.jackrabbit.oak.jcr.session.operation.ItemOperation.checkPreconditions(ItemOperation.java:34)
at
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:289)
at org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:113)
at org.apache.jackrabbit.oak.jcr.session.ItemImpl.getPath(ItemImpl.java:153)
at org.apache.jackrabbit.oak.jcr.session.NodeImpl.getPath(NodeImpl.java:99)
----------------------------------------------------------
----------------------------------------------------------
I tried closing and restarting the observer instance, but it still hasn't
registered the deleted node.
A new session is started every time an event is caught that deals with the
changed content, so it should not be a problem with session refresh.
Thanks,
Adrien
Re: clustering and synchronization
Posted by Marcel Reutegger <mr...@adobe.com>.
Hi,
On 25/10/14 23:41, "Adrien Lamoureux" <la...@gmail.com> wrote:
>What kind of delay is expected between cluster nodes when a change is made
>in one oak instance, and another oak instance needs to become aware of
>that
>change?
with the default configuration a cluster node should see changes from other
cluster nodes with a delay of roughly one second.
Regards
Marcel
Re: clustering and synchronization
Posted by Adrien Lamoureux <la...@gmail.com>.
Please disregard my last email. Turns out I was trying to access a node
that was just deleted. (I was logging the deleted node)
It's working great!
Adrien
On Sat, Oct 25, 2014 at 2:41 PM, Adrien Lamoureux <
lamoureux.adrien@gmail.com> wrote:
> Hello,
>
> What kind of delay is expected between cluster nodes when a change is made
> in one oak instance, and another oak instance needs to become aware of that
> change?
>
> How stable is clustering is Oak?
>
> I currently have 2 instances of Oak 1.0.7, both using a single instance of
> MongoDB 2.6.4, all running on the same system (locally)
>
> I deleted a node, and 30 seconds later or so, I made a change triggering
> an event that the other instance is listening for, but I get this:
>
> ----------------------------------------------------------
> ----------------------------------------------------------
>
> javax.jcr.InvalidItemStateException: This item does not exist anymore
>
> at
> org.apache.jackrabbit.oak.jcr.delegate.ItemDelegate.checkAlive(ItemDelegate.java:85)
>
> at
> org.apache.jackrabbit.oak.jcr.session.operation.ItemOperation.checkPreconditions(ItemOperation.java:34)
>
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:289)
>
> at
> org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:113)
>
> at
> org.apache.jackrabbit.oak.jcr.session.ItemImpl.getPath(ItemImpl.java:153)
>
> at
> org.apache.jackrabbit.oak.jcr.session.NodeImpl.getPath(NodeImpl.java:99)
>
> ----------------------------------------------------------
>
> ----------------------------------------------------------
>
> I tried closing and restarting the observer instance, but it still hasn't
> registered the deleted node.
>
> A new session is started every time an event is caught that deals with the
> changed content, so it should not be a problem with session refresh.
>
> Thanks,
>
> Adrien
>
>
>