httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Akins <bak...@web.turner.com>
Subject mod_proxy balancer maxattempts bug??
Date Fri, 11 Nov 2005 19:56:51 GMT
If I have the following:

<Proxy balancer://fill>
     BalancerMember http://10.165.80.90:80 max=256 timeout=3
     BalancerMember http://10.165.30.89:80 max=256 timeout=3
     BalancerMember http://10.165.80.88:80 max=256 timeout=3
     BalancerMember http://10.165.80.89:80 max=256 timeout=3
     BalancerMember http://10.165.30.91:80 max=256 timeout=3
     BalancerMember http://10.165.30.92:80 max=256 timeout=3
</Proxy>
 


and later:

ProxyPass / balancer://fill/ timeout=10 maxattempts=3 lbmethod=byrequests


if all 6 members are unreachable, but still "OK", proxy tries each 
member before giving up.  should it only try 3?

maybe some different logic needs to be mod_proxy?



  access_status = ap_proxy_pre_request(&worker, &balancer, r, conf, &url);
         if (access_status != OK) {
             /*
              * Only return if access_status is not HTTP_SERVICE_UNAVAILABLE
              * This gives other modules the chance to hook into the
              * request_status hook and decide what to do in this situation.
              */
             if (access_status != HTTP_SERVICE_UNAVAILABLE)
                 return access_status;
             /*
              * Ensure that balancer is NULL if worker is NULL to prevent
              * potential problems in the post_request hook.
              */
             if (!worker)
                 balancer = NULL;
             goto cleanup;
         }
         if (balancer && balancer->max_attempts_set && !max_attempts)
             max_attempts = balancer->max_attempts;

-- 
Brian Akins
Lead Systems Engineer
CNN Internet Technologies

Mime
View raw message