jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Balak Dev <balafor...@gmail.com>
Subject Re: Repository locked by one server in clustered mode
Date Mon, 07 Jul 2008 07:14:40 GMT

Hi Alex and Thomas,
                           
Thanks a lot for your help. We were able to get the clustered configuration
going.

I have few more doubts on the architecture part. We have the configuration
in such a way that everything is being pointed to the database. I mean the
Filesystem, persistance manager of the workspace, versioning and also search
index of the workspace and the cluster configuration.

If i look at my workspace, i have the workspace configuration file and a
folder called index. I guess the index is for the search part. 

1) I didnt understand where the actual data is being stored?

2) what is the role of Filesystem configuration?

3) what is the role of workspace when we are having the configuartions
pointing to database?

Thanks,
Bala.


Alexander Klimetschek wrote:
> 
> On Mon, Jun 30, 2008 at 6:44 AM, Balak Dev <balaforums@gmail.com> wrote:
>> We are actually using JBoss DROOLS, which internally uses Jack rabbit.
>>
>> We have both of our managed servers [nodes] running on a single machine
>> in a
>> single domain.
>>
>> I have few more questions here:
>>
>> a) The repository cannot be shared. So does it mean that i need to have a
>> seperate repository folder get created for each of the managed servers
>> [nodes]. If yes, then where is that i need to mention about it.
> 
> Yes. You need a database persistence manager that is transactional,
> which actually shares the data (see bottom of
> http://wiki.apache.org/jackrabbit/Clustering). The FileSystem's can be
> normal LocalFileSystem, because each node will store the separately.
> You need a different repository home for each cluster node, including
> a repository.xml that is typically the same except for the cluster id.
> Usage of ${rep.home} and ${wsp.home} will give the FileSystems
> different locations for each node and the PM configuration pointing to
> a database will point to the database as the shared location for the
> data.
> 
>>
>> b) Or is it that i can have a single repository folder, but have
>> different
>> cluster configurations.
>>
>> eg:- <Cluster id="mnage_server_1">
>>       ..........................
>>       </Cluster>
>>
>>       <Cluster id="manage_server_2">
>>       ..........................
>>       </Cluster> and so on...
>>
> 
> Regards,
> Alex
> 
> -- 
> Alexander Klimetschek
> alexander.klimetschek@day.com
> 
> 

-- 
View this message in context: http://www.nabble.com/Repository-locked-by-one-server-in-clustered-mode-tp18170869p18311243.html
Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.


Mime
View raw message