Mailing-List: contact commits-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: commits@jackrabbit.apache.org
Date: Fri, 03 Jul 2009 16:49:53 -0000
Message-ID: <20090703164953.1212.47173@eos.apache.org>
Subject: [Jackrabbit Wiki] Update of "Clustering" by AlexanderKlimetschek

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The following page has been changed by AlexanderKlimetschek:
http://wiki.apache.org/jackrabbit/Clustering

The comment on the change is:
added info on how clustering and datastore work together

------------------------------------------------------------------------------
- Clustering in Jackrabbit works as follows: content is shared between all cluster nodes. That means all Jackrabbit cluster nodes need access to the SAME persistent storage (persistence manager and data store). The [PersistenceManagerFAQ persistence manager] must be clusterable (eg. central database that allows for concurrent access); any DataStore (file or DB) is clusterable by its very nature, as they store content by unique hash ids. However, each cluster node needs its own (private) FileSystem and ["Search"] index.
+ Clustering in Jackrabbit works as follows: content is shared between all cluster nodes. That means all Jackrabbit cluster nodes need access to the SAME persistent storage (persistence manager and data store).
+ 
+ The persistence manager must be clusterable (eg. central database that allows for concurrent access, see ["PersistenceManagerFAQ"]); any DataStore (file or DB) is clusterable by its very nature, as they store content by unique hash ids. However, each cluster node needs its own (private) FileSystem and ["Search"] index.
  
  Every change made by one cluster node is reported in a journal, which can be either file based or written to some database.
  
@@ -11, +13 @@

   * Each cluster node must have its own repository configuration
   * Every cluster node must be assigned a unique ID
   * A journal type must be chosen, either based on files or stored in a database
-  * The persistence managers must store their data in the same, globally accessible location
+  * The persistence managers must store their data in the same, globally accessible location (see ["PersistenceManagerFAQ"])
+  * A DataStore must always be shared between nodes, if used
  
  === Unique Cluster Node ID ===