On 16/02/2010 07:01, Mladen Turk wrote: > On 02/16/2010 12:24 AM, Mark Thomas wrote: >> On 15/02/2010 21:52, Filip Hanik - Dev Lists wrote: >>>> >>> why not just a servlet filter? >> >> +1. I was going to suggest the same thing. >> > > Why not reusing the clustering code for that. > It would allow to pre-redirect the requests > without doing the actual ping for undeployed > applications or for the instances going down. > Just having filter would be enough to get the > info about the single node, but the highest > latency in mod_jk comes from detecting the failed > node not the busiest one.
I don't see why the current set of valid cluster nodes could not be passed back via a header. That raises the interesting question of if a node goes down, which component will notice first? The proxy or the cluster? With long timeouts in the proxy, there is a good chance the cluster will notice quite some time earlier so there is a definite advantage to this. The other thing it potentially allows is the cluster to tell the proxy about which nodes are in the cluster, allowing a more dynamic configuration. Not sure I'd want to use that in production, but in dev that could be useful. All of this / some of this could make a great GSOC project. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
