Tomcat 4/5 Clustering. 2003-10-10 - By Nathan Christiansen
Back
Filip,
Thanks for the link to your site on Tomcat clusters.
Are there any preliminary results about cluster size vs. replication traffic
and limitations?
If I remember right, the limit for load balancing clusters using an older
method was about 6 servers in your cluster before the session object
replication became the bottleneck.
It was this reason alone that I stopped using the session object to store
session info. I store my persistent objects to a MySQL database, using a
session cookie as the key to the database row.
Are there plans to support Session Object storage in a database (like my method
of storing persistent objects)?
This would allow massive scalability in the cluster, since the 'dirty' session
object only needs to be sent to one place instead of to all the Tomcat servers
in the cluster.
I realize that this introduces a problem in that every single server in the
cluster needs to be running the same version of Tomcat in order to have session
objects serialize and deserialize properly. Or that you will need to use
another storage format other than simple serialization and deserialization.
-- Nathan Christiansen
Tahitian Noni International
http://www.tahitiannoni.com
-- --Original Message-- --
From: Filip Hanik [mailto:devlists@(protected)]
Sent: Friday, October 10, 2003 10:20 AM
To: Tomcat Users List
Cc: jmoliere@(protected); hanasaki@(protected)
Subject: Re: Clustering Tomcat - Loadbalancing and Failover
http://cvs.apache.org/~fhanik/
> how are session states replicated?
once, after the entire request is completed. If the session is not dirty, no
replication will be done
Doesn't use java groups, instead pure UDP/TCP.
Filip
-- Nathan Christiansen
Tahitian Noni International
http://www.tahitiannoni.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)
|
|
