Hi Chetan and Oliver,
Thanks for the replies. So assuming that I don't connect over RMI, does this
mean there is no way around this problem apart from delaying operations a few
seconds? If multiple Node Stores are being used, then it seems reasonable that
the backend is queried periodically, hence the lag, but is there a way to use
the same Node Store when connecting through an Oak application?
Furthermore, as for connecting over RMI: the reason why I abandoned that cause
was because unlike in Sling 7, where I configured the Apache Sling JCR
Repository RMI Registrar on port 1099 and saved it to expose the repository
over RMI, it did not work in Sling 8. Neither do I see a Jackrabbit/Oak folder
on my local machine, though the logs do state that RMI over 1099 is enabled.
I've confirmed by attempting to telnet into "localhost 1099", which works when
RMI is enabled in Sling 7 but not when it is in Sling 8.
> Date: Wed, 2 Dec 2015 17:22:31 +0530
> Subject: Re: Sling retrieving out-of-date data
> From: chetan.mehro...@gmail.com
> To: users@sling.apache.org
>
> On Wed, Dec 2, 2015 at 4:13 PM, Oliver Lietz <apa...@oliverlietz.de> wrote:
> > Thanks, Chetan. Is it really the _new Oak_ or the new NodeStore which sets
> > up
> > a cluster?
>
> Its new NodeStore
>
> > The Oak documentation for clustering could be more expressive...
>
> Yes docs are not upto the mark. Would try to find some time and update them
>
>
> Chetan Mehrotra
