Created attachment 35064 [details] fix patch Fix patch that reflects changes in loadfactor when glaceful * phenomenon (1) apachectl start <Proxy balancer://mycluster/> BalancerMember http://127.0.0.1:8081 loadfactor=10 BalancerMember http://127.0.0.1:8082 loadfactor=10 </Proxy> (2) http://127.0.0.1/balancer-manager Worker URL Route RouteRedir Factor Set Status Elected To From http://127.0.0.1:8081 10 0 Ok 0 0 0 http://127.0.0.1:8082 10 0 Ok 0 0 0 (3) ab -n 500 -c 5 http://localhost/index.html (4) http://127.0.0.1/balancer-manager Worker URL Route RouteRedir Factor Set Status Elected To From http://127.0.0.1:8081 10 0 Ok 250 49K 20K http://127.0.0.1:8082 10 0 Ok 250 49K 20K (5) apachectl graceful <Proxy balancer://mycluster/> BalancerMember http://127.0.0.1:8081 loadfactor=10 BalancerMember http://127.0.0.1:8082 loadfactor=5 BalancerMember http://127.0.0.1:8083 loadfactor=10 </Proxy> (6) http://127.0.0.1/balancer-manager Worker URL Route RouteRedir Factor Set Status Elected To From http://127.0.0.1:8081 10 0 Ok 250 49K 20K http://127.0.0.1:8082 10 0 Ok 250 49K 20K http://127.0.0.1:8083 10 0 Ok 0 0 0 (7) ab -n 500 -c 5 http://localhost/index.html (8) http://127.0.0.1/balancer-manager Worker URL Route RouteRedir Factor Set Status Elected To From http://127.0.0.1:8081 10 0 Ok 417 81K 33K http://127.0.0.1:8082 10 0 Ok 417 81K 33K http://127.0.0.1:8083 10 0 Ok 166 32K 13K * after patch (1) apachectl start <Proxy balancer://mycluster/> BalancerMember http://127.0.0.1:8081 loadfactor=10 BalancerMember http://127.0.0.1:8082 loadfactor=10 </Proxy> (2) http://127.0.0.1/balancer-manager Worker URL Route RouteRedir Factor Set Status Elected To From http://127.0.0.1:8081 10 0 Ok 0 0 0 http://127.0.0.1:8082 10 0 Ok 0 0 0 (3) ab -n 500 -c 5 http://localhost/index.html * http://127.0.0.1/balancer-manager Worker URL Route RouteRedir Factor Set Status Elected To From http://127.0.0.1:8081 10 0 Ok 250 49K 20K http://127.0.0.1:8082 10 0 Ok 250 49K 20K (4) apachectl graceful <Proxy balancer://mycluster/> BalancerMember http://127.0.0.1:8081 loadfactor=10 BalancerMember http://127.0.0.1:8082 loadfactor=5 BalancerMember http://127.0.0.1:8083 loadfactor=10 </Proxy> (5) http://127.0.0.1/balancer-manager Worker URL Route RouteRedir Factor Set Status Elected To From http://127.0.0.1:8081 10 0 Ok 250 49K 20K http://127.0.0.1:8082 5 0 Ok 250 49K 20K http://127.0.0.1:8083 10 0 Ok 0 0 0 (6) ab -n 500 -c 5 http://localhost/index.html * http://127.0.0.1/balancer-manager Worker URL Route RouteRedir Factor Set Status Elected To From http://127.0.0.1:8081 10 0 Ok 450 87K 36K http://127.0.0.1:8082 5 0 Ok 350 68K 28K http://127.0.0.1:8083 10 0 Ok 200 39K 16K (7) apachectl graceful <Proxy balancer://mycluster/> BalancerMember http://127.0.0.1:8081 loadfactor=10 BalancerMember http://127.0.0.1:8083 loadfactor=10 </Proxy> (8) http://127.0.0.1/balancer-manager Worker URL Route RouteRedir Factor Set Status Elected To From http://127.0.0.1:8081 10 0 Ok 450 87K 36K http://127.0.0.1:8083 10 0 Ok 200 39K 16K (9) ab -n 500 -c 5 http://localhost/index.html (10) http://127.0.0.1/balancer-manager Worker URL Route RouteRedir Factor Set Status Elected To From http://127.0.0.1:8081 10 0 Ok 700 136K 56K http://127.0.0.1:8083 10 0 Ok 450 87K 36K
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.