DNS update times are too long to trust on them
If you want to have two installations, and direct users to
the one is working, you might have one IP address for the
machine that is in service at a given time, and switch that
address between the two machines as appropriate, NOT changing
the DNS, i.e., change the IP address of the Tomcat server.
Gustavo Avitabile
On Mon, May 9, 2011 at 6:17 AM, Brian Braun <brianbr...@gmail.com> wrote:
Hi,
I'm about to launch a service on the internet, using Tomcat 7. This service
should be available 24x7, it should never be unavailable (or virtually
never). However, I will definitely be improving and correcting my app
frequently, so I will have to republish the WAR file very often. Not even
considering the fact that my app has leaking problems (that's another story)
and therefore I will have to restart Tomcat itself, republishing the app
will make it unavailable for at least 10 seconds while I do it.
I'm thinking that I need to create a Tomcat Cluster. Is that the way to go?
Any opinions?
Another idea would be to have two tomcat installations, and to change the IP
my domain points to, to the IP that goes to that other Tomcat instance. But
changing the IP takes some time and I would have to wait until I think that
the DNS servers have updates the new IP, that would be slow and unreliable.
Thanks in advance,
Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
