[EMAIL PROTECTED] wrote:
I was wondering about repository clustering and its implementation.
Pretend the following situation:
Repo A and Repo B are in a cluster.
Frontend A connects to Repo A and Frontend B connects to Repo B.
Every change to Repo B is propagated to Repo A, which propagates it to Frontend
A. This works. :)
Repo A goes down.
Changes to Repo B occur and will be posted to the cluster topic.
Repo A goes up again and starts reading the messages from the cluster topic.
Will these message be propagated to Frontend A?
Yes. When the repository processes the messages it will also send the
notifications to the connected sites and CMSes.
Will this also happen when the slide index files were removed between the
shutdown and startup of Repo A?
I'm not 100% sure. It's probably a good idea to shutdown the connected
sites during the rebuild of the index, because search results from the
sites will give incomplete results.
Regards,
Bart
With regards,
Nick S.
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
--
Hippo B.V. - Amsterdam
Oosteinde 11, 1017 WT, Amsterdam, +31(0)20-5224466
Hippo USA Inc. - San Francisco
101 H Street, Suite Q, Petaluma CA, 94952-3329, +1 (707) 773-4646
-----------------------------------------------------------------
http://www.onehippo.com - [EMAIL PROTECTED]
-----------------------------------------------------------------
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
