DO NOT REPLY [Bug 37246] New: - Election method T weirdness under constant heavy load

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37246>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37246

           Summary: Election method T weirdness under constant heavy load
           Product: Tomcat 5
           Version: Unknown
          Platform: Other
               URL: http://algesten.blogspot.com/
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Native:JK
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: puckman@taglab.com


Election method T is electing a worker depending on the amount of traffic to the workers. If we put a 
constant load on the server using ab -c 150 -n 1000000 http://my.site/page.

By refreshing the jkstatus page a lot we're obvserving that this election method choses the same worker 
for all requests for around a second or so, effectively having 150 long busy queue on one worker whilst 
the others are at 0. In other words we're blitzing one worker with the whole load at a time.

I can only speculate to why this is, but if for instance the traffic counters on the workers are only updated 
every second, simply looking at those counters would elect the same worker for a second at a time.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org