Hi St�phane,
Thanks
for your comments.
I've
considered that scenario but - if I understand you correctly - it really just
shares load and adds an element of redundancy. If server B goes away it doesn't
matter because server A is still there. If Jahia/Tomcat fails on server A it
likewise doesn't matter. But if server A dies (i.e. completely: like a ahrdware
failure) you still lose the website.
No?
So I
agree it's an improvement but it's not quite perfect.
I was
hoping there was a way to wake Jahia up to the fact that its filesystem
repository had changed without restarting it. Maybe this is not
possible...
:(
Chris
-----Original Message-----
From: St�phane Croisier [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 18 January 2005 11:09 PM
To: [email protected]
Subject: Re: replicating Jahia servers for redundancy purposes
Hi Chris,
Wouldn't it be more easy to install two Jahia server in a load balancing environement. On the Server A, you would have the full stack (Jahia; Tomcat; Database + File System) and on the Server A, you would have only a Jahia + Tomcat runnning (with DB + FS mounted on server A).
The risk that the DB or the FS fail is lower than the risk that the Java stack fails so you would have no high availability for these elements but this should be fine, no? Moreover you will have better overall performance has the load will be split between the two servers. Finally this does not require more servers (just 2 like the configuration you were speaking about).
My 2cts
St�phane
At 07:54 18/01/2005, you wrote:
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
