On 15.09.2009 15:32, balakarthik.baska...@wipro.com wrote: > Hi Rainer, > > The other possible configuration that I think probably we might be > lacking/quite different is that we are loadbalancing the requests among > 240 worker nodes each pointing to one app instance (all app instances > available in the default cluster) and we use Busyness algorithm(for load > balancer worker). > > We have seen partial content from the middle of the pages as well which > was quite difficult to simulate in my local setup. > > Do you think load balancing among 240 workers could be a possibiltiy of > messing up with request responses/adding up delay when there is a > failover/other load balancing situations? (Or) is there a defined limit > of worker nodes to be balanced that have been identified/defined?
There is no builtin limit. Adding a lot of workers, makes things a bit slower, though in reality the time needed for the balancing should be very small compared to the time needed to actually server the requests. Using 240 Tomcat nodes will drive up your management cost (what's the state of all nodes etc.). I generally prefer the "R" method of balancing (by requests) but opinions vary w.r.t. the optimal method. I am not aware of issues concerning "partial content from the middle of the pages". Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
