Hi, Our current system has two servers in a clustered environment with shared disk, but we ended up splitting the webapps areas into seperate.
This gave us more control in the end and our promote procedure for a new version of an app is now scripted. So one server gets removed from the pool of active servers, upgraded and then replaced and the script moves to the next. We still need a full outage for things that require a schema change in the backend for example. But we do a sorry server page while the brief outage is underway. For a bigger site, you could go 2 clusters and have shared disk in each cluster. Pull one cluster at a time out of your load balancer and use the shared disk to trigger an upgrade. You'd have to pick a lull time in your load though so half the system could cope. It helps that half our system can carry the full load as we run a stretched cluster 150m apart for DR purposes. 150m isn't enough, but it's better than the same room. I've never played with the farm deployer module, not sure if thats an alternative. I'd be interested if anyone has? Or solved the problem another way. Hope that helps, Dave -- David Nillesen Systems Administrator http://njorsk.com On Thu, Aug 26, 2010 at 11:57 PM, Luca Gervasi <tom...@ashetic.net> wrote: > On Wed, 2010-08-25 at 10:50 -0300, Fernando Morgenstern wrote: > > Hi, > > > > I have a Tomcat cluster environment with 4 servers. I was wondering that > is the best way to deploy an application on 4 servers at the same time. > > > > > At a first moment, i thought about having a script that would copy war > files to all servers using rsync. Basically i upload the war file to the > first server and them use this script to copy to other tomcat servers. > > > > > Could you share your experience with this kind of environment? Is this > the best way to deal with deployment? > > > > Thank you, > > > > Fernando M. Morgenstern > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > In such enviroment i think that you should deploy once in the NAS/SAN (i > mean, unpack the war) and use the shared filesystem in ro in each > istance. > > Btw i'm pretty interested in more answers :) > > See Ya > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org >
