mod_jk: load balancer == bottleneck?


Performance and scalability: mod_jk: load balancer == bottleneck?

  1. mod_jk: load balancer == bottleneck? (1 messages)


    This may be a naive on my part, but consider the following general clustering scenario pictured in jonas project's docs:

    a couple of questions:
    -i understand every request coming in goes through apache LB; does the *response* go through apache as well, or is it going from a selected tomcat directly to the requesting machine?

    -isn't Apache node itself going to become the bottleneck at some point - if enough tomcats nodes are placed behind it? Assuming all nodes are computers of same configurations, how many nodes can be placed behind one Load Balancing node, before it becomes a bottleneck?

    thanks a lot
    ps. i'd really appreciate any/all pointers (to other docs/articles) on web-tier clustering.
  2. Yes. Your concerns are valid.

    Let me put my 2Cs here.
    When we tried a similar clustering scenario the mod_jk was doing a round robin load balance only it was no true load balancing as such. But the version we were experimenting was Tomcat3.2.x But I am not sure how much of this was enhanced in Catelina and the later versions.

    Regarding the responses... to my knowledge, yes they will be sent from Apache only. because the client has no access to the mod_jk communication happening via the engines. So I am pretty sure at one point it will become a bottleneck. That's where I believe hardware load balancing devices come into play. In which they will do the real request handling and you will have enough of those cluster setup to handle the requests.
    Note1: There may be other alternatives which I am not aware of.
    Note2: take a look at F5 Networks for HW LB products

    -vaheesan selvarajah