Anonymous | Login | Signup for a new account | 11-22-2024 09:40 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0000064 | [Resin] | minor | always | 03-30-05 00:00 | 05-11-05 00:00 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | |||||||||
Priority | urgent | Resolution | fixed | ||||||
Status | closed | Product Version | 3.0.12 | ||||||
Summary | 0000064: add strict round-robin policy to HmuxLoadBalanceServlet | ||||||||
Description |
RSN-55 (rep by Dan Schwalbe) As a related note, the round robin strategy that the resin load balancer is using is not working very well for us. It is judging how busy the server is by how much date is being streamed to the client. So the load balancer is almost always choosing the same backend server. In fact, little of our processing involves streaming data. A much simpler round robin strategy which would always move to the next server would be much better for us. Would it be possible to use such a strategy? |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Issue History | |||
Date Modified | Username | Field | Change |
03-30-05 00:00 | ferg | New Issue | |
11-30-05 00:00 | administrator | Fixed in Version | => 3.0.13 |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
30 total queries executed. 28 unique queries executed. |