It might be a late reply but we i saw at least in JR 2.0 is that when
session.save() happens it also forces a sync first so that the JR node gets
up-to-date first.
We also see the degradation in performance the more nodes we put in the
cluster. The global lock forces to make every session.save()
Hi,
automatic sync and the manual Session.refresh() have essentially the
same result?
I think so.
Should this be something you should know?
I don't plan to find out, sorry. I didn't write the cluster code, and
I don't feel responsible for it :-)
Regards,
Thomas
Hi all,
We are setting up a clustered Jackrabbit environment as the data storage
for our (custom) CMS. We are using Jackrabbit 1.6.0 with an Oracle 10g
database, bundled persistence manager and finegrained ISM locking.
Whenever the repository is accessed through a JcrSession, we first do a
Hi,
The automatic sync is periodic (once every few seconds).
Session.refresh() will force an immediate cluster sync. I'm not sure
if the immediate cluster sync on Session.refresh() is a good idea, but
that's how it's implemented currently.
- Why is a refresh more expansive when there are more
