You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Walter Raboch (JIRA)" <ji...@apache.org> on 2005/07/15 13:38:13 UTC
[jira] Commented: (JCR-169) Make Jackrabbit clusterable
[ http://issues.apache.org/jira/browse/JCR-169?page=comments#action_12315903 ]
Walter Raboch commented on JCR-169:
-----------------------------------
- extending LockManager to sync locks with other Nodes
- extending the ORM Layer (Hibernate with shared caching for performance) to save to a central DBMS
(just working on this part)
OR
- Implement some sort of replication - so each node has an own filebased persistence
manager and the content is replicated to each node
- extending ObservationManager to send and receive Events to and from other nodes
- Lucene should be indepentend on each node but be aware of new nodes and changes.
- Config - the cluster should have a central place for config management
- some intelligence in the JCR-RMI client to find a content repository node from the cluster
dependending on node state (load, shutdown, ...)
> Make Jackrabbit clusterable
> ---------------------------
>
> Key: JCR-169
> URL: http://issues.apache.org/jira/browse/JCR-169
> Project: Jackrabbit
> Type: New Feature
> Components: core
> Reporter: Marcel Reutegger
> Priority: Minor
>
> This jira issue discusses the technical implications on the current design of Jackrabbit to introduce clustering.
> Particularly the following areas require thorough investigation:
> - SharedItemStateManager and its cache
> - cache integrity
> - cache design: look aside, write through?
> - hook for distributed cache, interface?
> - isolation level
> - transaction integrity within Jackrabbit, interaction with transient layer
> - VirtualItemStateProvider
> - same strategy as SharedItemStateManager?
> - Search index
> - single or per cluster node index?
> - Observation
> Please state more areas if needed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira