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, 31 May 2010 07:09:58 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.
http://wiki.apache.org/jackrabbit/Clustering?action=diff&rev1=22&rev2=23

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

  
  === Persistence Manager Configuration ===
  
- For performance reasons, only information identifying the modified items is stored in the
journal. This implies, that all cluster nodes must have access to the items' actual content.
The persistence manager needs to be transactional, and need to support concurrent access from
multiple processes. When using Jackrabbit, one option is to use a database persistence manager,
and use a database that does support concurrent access. The file system based persistence
managers in Jackrabbit are not transactional and don't support concurrent access; Apache Derby
doesn't support concurrent access in the embedded mode. The following sample shows a workspace's
persistence manager configuration using an Oracle database:
+ All cluster nodes must point to the same persistence location. For performance reasons,
only information identifying the modified items is stored in the journal. This implies, that
all cluster nodes must configure the same persistence manager and persistence location, because
they must have access to the items' actual content. The persistence manager needs to be transactional,
and need to support concurrent access from multiple processes. When using Jackrabbit, one
option is to use a database persistence manager, and use a database that does support concurrent
access. The file system based persistence managers in Jackrabbit are not transactional and
don't support concurrent access; Apache Derby doesn't support concurrent access in the embedded
mode. The following sample shows a workspace's persistence manager configuration using an
Oracle database:
  
  {{{
  <PersistenceManager class="org.apache.jackrabbit.core.persistence.db.OraclePersistenceManager">
@@ -145, +145 @@

  </PersistenceManager>
  }}}
  
- The data store should be used to store large binaries (all cluster nodes need to access
the same data store). When not using the data store, one need to set the parameter '''externalBLOBs'''
to ''false'' so that large binaries are stored in the persistence manager. The file system
blob store does not support clustering, because it uses a local directory.
+ === Data Store Configuration ===
  
+ All cluster nodes must point to the same data store location. The data store should be used
to store large binaries (all cluster nodes need to access the same data store). When not using
the data store, one need to set the parameter '''externalBLOBs''' to ''false'' so that large
binaries are stored in the persistence manager. The file system blob store does not support
clustering, because it uses a local directory.
+ 

Mime
View raw message