You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Dominique Pfister (JIRA)" <ji...@apache.org> on 2007/08/15 17:35:33 UTC
[jira] Updated: (JCR-1060) New workspaces created in 1 cluster node
are not automatically available in other cluster nodes
[ https://issues.apache.org/jira/browse/JCR-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominique Pfister updated JCR-1060:
-----------------------------------
Priority: Minor (was: Major)
Issue Type: Improvement (was: Bug)
Lowered issue type and priority as the creation of new workspaces is not part of the standard JCR API.
> New workspaces created in 1 cluster node are not automatically available in other cluster nodes
> -----------------------------------------------------------------------------------------------
>
> Key: JCR-1060
> URL: https://issues.apache.org/jira/browse/JCR-1060
> Project: Jackrabbit
> Issue Type: Improvement
> Components: clustering
> Affects Versions: 1.3.1
> Environment: Affects all environments. We're testing with Fedora Core 4, Mysql, Tomcat 5.0.30 and JDK 1.5.0_11
> Reporter: Shaun Barriball
> Priority: Minor
>
> New workspaces are not clustered.
> Creating a new workspace (Workspace2) on node A does not result in a new workspace being created on node B e.g.
> Node A file system:
> Repository
> Version
> Workspaces
> Workspace1
> Workspace2
>
> Node B file system:
> Repository
> Version
> Workspaces
> Workspace1
> This is problem for us as new workspaces are being created all the time, hence they must be automatically clustered.
> I'm guessing this problem occurs as the "create workspace" mechanism is JackRabbit specific and is outside of the JCR spec and event model?
>
> Potential solutions:
> . Move to a DatabaseFileSystem - there are a couple of disadvantages
> to this for us. We like to be able to view and amend the files and in particular we regularly updated the custom_nodetypes.xml with new types as part of an upgrade process. Presumably the nodes types would be less accessible within the database.
> . Use a Network File Share for local files - we're trying to achieve
> the simplest solution for fault tolerance therefore we'd rather avoid the complication of filesystem replication schemes (Linux DRBD etc) or the expense of SAN solutions.
> . Manually create copy new workspaces - also not really an option as
> new workspaces are created all the time
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.