Hi Jörg, yes, this is what i meant when I said that it is not possibly to add new node easily (despite the title of that wiki page). Without Janitor you can just snap in new node and it will sync itself, with Janitor you need to bring down one node to add another. Anyway thanks a lot for providing the link to setting up new node with Janitor on. That makes this thread really complete.
Cheers -- Jan On Apr 17, 2013, at 5:09 PM, Jörg von Frantzius <[email protected]> wrote: > Hi Jan, > > is it > http://wiki.apache.org/jackrabbit/Clustering#Easily_add_new_cluster_nodes > that describes adding new cluster nodes after a janitor has run? Since the > index is copied, it sounds like it would work even if the janitor has run. > > Regards, > Jörg > > > On 12.04.2013 10:14, Jan Haderka (via Magnolia Forums) wrote: >> Yeah, that happens when you don't have janitor running. >> >> Before enabling it, I suggest you read JR documentation at >> http://wiki.apache.org/jackrabbit/Clustering#Removing_Old_Revisions >> since there are some known caveats to enabling the janitor: >> - If the janitor is enabled then you loose the possibility to easily add >> cluster nodes. (It is still possible but takes detailed knowledge of >> Jackrabbit.) >> - 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. >> - If a cluster node is removed permanently from the cluster, then its entry >> in the LOCAL_REVISIONS table should be removed manually. Otherwise, the >> clean-up thread will not be effective. >> >> Afaik the sync condition only concerns the very first time the clean-up task >> runs, so setting >> <param name="janitorFirstRunHourOfDay" value="3"/> >> meaning 3:00am or any time when it is sure editors don't add content, should >> provide a reasonable guarantee that all cluster nodes will have already >> written their local revision to the db. Or maybe you have power to restrict >> all write access for the time you decide to enable it. >> >> Unfortunately there is no flag or command that would force all >> instances/nodes to push their local changes to the journal. However it is >> safe to assume that if there are no editors logged in and no scheduled tasks >> executed for extended period of time (10-20 minutes) all the instances have >> already pushed their local updates and you can enable the janitor. >> >> With MySQL as a DB (and possibly others), you might have to use OPTIMIZE >> TABLE afterward to free up disk space with InnoDB tables. >> >> HTH, >> Jan >> >> > > > -- > Dipl. inf. Jörg von Frantzius, System Architect > > Email mailto:[email protected] > Phone +49 30 283921-318 > Fax +49 30 283921-29 > > Aperto AG - In der Pianofabrik > Chausseestraße 5, D-10115 Berlin-Mitte > http://www.aperto.de > http://www.facebook.com/aperto > https://www.xing.com/companies/apertoag > > HRB 77049, AG Berlin Charlottenburg > Vorstand: Dirk Buddensiek (Vorsitzender), Kai Großmann, Stephan Haagen > Aufsichtsrat: Bernd Hardes (Vorsitzender) > > > ---------------------------------------------------------------- > For list details, see http://www.magnolia-cms.com/community/mailing-lists.html > Alternatively, use our forums: http://forum.magnolia-cms.com/ > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
