jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jackrabbit Wiki] Update of "Clustering" by ThomasMueller
Date Mon, 16 Aug 2010 12:10:17 GMT
Dear Wiki user,

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

The "Clustering" page has been changed by ThomasMueller.
The comment on this change is: use shared repository-level file system.
http://wiki.apache.org/jackrabbit/Clustering?action=diff&rev1=23&rev2=24

--------------------------------------------------

  
  == Overview ==
  
- 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).
+ 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, data store, and repository file system).
  
- 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.
+ 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) workspace 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.
  
@@ -21, +21 @@

  In order to use clustering, the following prerequisites must be met:
  
   * Each cluster node must have its own repository configuration.
+  * A DataStore must always be shared between nodes, if used.
+  * The FileSystem on the repository level must be shared (only the one that is on the same
level as the data store; only in the repository.xml file).
+  * Each cluster node needs its own (private) workspace level and version FileSystem (only
those within the workspace and versioning configuration; the ones in the repository.xml and
workspace.xml file).
-  * Each cluster node needs its own (private) FileSystem and Search index. 
+  * Each cluster node needs its own (private) Search indexes.
   * Every cluster node must be assigned a unique ID.
   * A journal type must be chosen, either based on files or stored in a database.
+  * Each cluster node must use the same (shared) journal.
   * 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 ==
  

Mime
View raw message