On 21/03/2012 09:15, Dhaval Jaiswal wrote: > We have already server.xml(changed as per tomcat site instructions) > in place, but it is not working properly. I will give you detail idea > about our environment. > > We have 10 tomcats starting from 192.168.3.1 to 192.168.3.10. I > wanted to make 192.168.3.10 as master/backup node, which has a > session id information of rest 9 tomcats including 10 too. > > Kindly provide the clear example of server.xml of 192.168.3.10 > (master/backup node) & rest of the 9 tomcats.
The backup manager doesn't work the way you think it does. Consider a four node cluster with nodes A, B, C & D. If node A has 30 primary sessions (more on that on a sec) then 10 of them will be backed up on node B, 10 on node C and 10 on node D. Sessions may be primary (currently being used), backup (full copy of the primary) or proxy (no data but knows which nodes are primary and backup). If a node isn't the primary or a backup it will be a proxy. You have to use sticky sessions with the backup manager else the primary node for the session keeps changing and that creates a lot of traffic. If the primary node fails, any other node can take over since they all have either a backup or the proxy info. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
