2011/2/7 Dertinger, Matthew <[email protected]>
> For the shared Datastore, I've accomplished this in the past my having an
> NFS mount on my second second server that points to the datastore on my
> first server. If you haven't already done so, it's a good idea to set
> ${magnolia.repositories.home} to a location outside of your webapp, to do
> so, open up WEB-INF/config/magnoliaPublic/magnolia.properties and edit the
> magnolia.reposities.home property, it should be something like the
> following:
>
> # set to a value outside the webapp to not loose the data on redeploys
> magnolia.repositories.home=/usr/local/magnolia-repos/public/repositories
>
Many thanks, now my cluster is working correctly, with any error or
exception in logs!
I tried the solution you proposed for the shared Datastore, but it didn't
work for me.
I think this is because if you redefine ${magnolia.repositories.home} by
editing WEB-INF/config/magnoliaPublic/magnolia.properties, it modifies also
${wsp.home} that appears in jackrabbit-bundle-mysql-search-pub1.xml and
jackrabbit-bundle-mysql-search-pub2.xml as follows:
<SearchIndex class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
<param name="path" value="${wsp.home}/index" />
.....
</SearchIndex>
In this way you share the search indexes of the two public instances in the
cluster, that I think must be private.
I solved removing the line above in
WEB-INF/config/magnoliaPublic/magnolia.properties and defining shared
repository in jackrabbit-bundle-mysql-search-pub1.xml and
jackrabbit-bundle-mysql-search-pub2.xml as follows:
<DataStore
class="org.apache.jackrabbit.core.data.FileDataStore">
<!-- <param name="path" value="${rep.home}/repository/datastore"/> -->
<param name="path" value="/magnolia-repos"/>
<param name="minRecordLength" value="1024"/>
</DataStore>
Where /magnolia-repos is an NFS share on the same machine who hosts the
MySQL db (not which one who runs the author and public instances, nor the
one who runs the clustered public instance, in my case).
Hope this could be helpful to someone.
I still have the cluster id in an "unset" state, as you can see in
catalina.out:
2011-02-08 12:13:21,981 INFO
info.magnolia.jackrabbit.ProviderImpl : Loading repository at
/var/lib/tomcat/apache-tomcat-6.0.30/webapps/magnoliaAuthor/repositories/magnolia
(config fil
e:
/var/lib/tomcat/apache-tomcat-6.0.30/webapps/magnoliaAuthor/WEB-INF/config/repo-conf/jackrabbit-bundle-mysql-search.xml)
- cluster id: "<unset>"
But, as I said, it seems that everything is working properly. Could I ignore
this INFO?
Many thanks again for your help, guys!
Bye.
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
