Hi folks,
I have a Jahia website running and I wish to make it a more robust solution.
Currently we have another server that aims to be a "close clone", or perhaps a psudo-clone (we call it a replicant): it's at a different IP address and every ten minutes it does rsyncs and a simple form of MySQL replication (I confess I couldn't get the MySQL replication to work!) to keep the two in sync. The plan is to change the DNS if the main server falls over so that the replicant becomes the live server.
This all works fine - although it's an inelegant solution - except that the parts of the Jahia content repository that are stored in the filesystem do not appear in the website until Jahia is restarted.
I had thoughts of placing a load balancer in front of this arrangement but this won't work if the replicant Jahia won't properly "see" some of the new content.
Is there a way to make Jahia re-read the filesystem-based parts of the repository without restarting Tomcat?
Or is there a better way to do this? I've looked at the clustering document but the only way to make this truly redundant is with several more servers and I can't do that.
Thanks for any help in advance,
Chris
Chris Stephens > Technology Director
email > [EMAIL PROTECTED]
phone > +61 2 9779 0129
mobile > +61 403 074 567
fax > +61 2 9779 0199
http://www.netreturn.com.au
