You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Liang <mo...@126.com> on 2016/11/01 02:16:50 UTC

About Jackrabbit cluster

Hi, all
   In our cluster environment, the Journal is very huge (about 60g), so we'd like to enalbing janitor configuration into repository.xml. As the wiki page said, there are 3 caveats after enabling the janitor. I can understand the first and third caveat, but not quite catch the second one as below. What does it mean? Does it mean we need do some extra thing (coding, configuration??) to make sure enabling janitor can work well?
  
You must make sure that all cluster nodes have written their local revision to the database before the clean-up task runs for the first time because otherwise cluster nodes might miss updates (because they have been purged) and their local caches and search-indexes get out of sync.


What I expected is that we only need to add janitorEnabled=true, janitorSleep and janitorFirstRunHourOfDay under Cluster element, and then the journal table could be purged as expected and no extra work that needs us to do


Please help me! Thanks.


Regards,
-Liang

Re: About Jackrabbit cluster

Posted by modelrepository <mo...@126.com>.
Thanks a lot.
If our cluster environment is planed to add two nodes, let's say node0 and
node1. Does the statement mean if we start node0 first, then before adding
and starting node1 into environment, the janitor thread could not be start,
since if it was started, then some journals from node0 will be deleted. Then
when starting node1 later, node1 will not catch the previous journals
created by node0?


Regards,
-Liang



--
View this message in context: http://jackrabbit.510166.n4.nabble.com/About-Jackrabbit-cluster-tp4665300p4665747.html
Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.

Re: About Jackrabbit cluster

Posted by Marcel Reutegger <mr...@adobe.com>.
Hi,

there should be a LOCAL_REVISIONS table in your database that contains a 
revision for each of your connected Jackrabbit cluster nodes. Please 
double-check this table exists and has entries for each of the cluster 
nodes. The Journal Janitor will use the data in this table to decide up 
to which revision it can clean the journal.

Regards
  marcel

On 01/11/16 03:16, Liang wrote:
> Hi, all
>    In our cluster environment, the Journal is very huge (about 60g), so
> we'd like to enalbing janitor configuration into repository.xml. As the
> wiki page said, there are 3 caveats after enabling the janitor. I can
> understand the first and third caveat, but not quite catch the second
> one as below. What does it mean? Does it mean we need do some extra
> thing (coding, configuration??) to make sure enabling janitor can work well?
>
>
>   * You must make sure that all cluster nodes have written their local
>     revision to the database before the clean-up task runs for the first
>     time because otherwise cluster nodes might miss updates (because
>     they have been purged) and their local caches and search-indexes get
>     out of sync.
>
>
> What I expected is that we only need to
> add janitorEnabled=true, janitorSleep and janitorFirstRunHourOfDay under
> Cluster element, and then the journal table could be purged as expected
> and no extra work that needs us to do
>
> Please help me! Thanks.
>
> Regards,
> -Liang
>
>
>
>