Mantis - Resin
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
64 minor always 03-30-05 00:00 05-11-05 00:00
Reporter: ferg Platform:  
Assigned To: OS:  
Priority: urgent OS Version:  
Status: closed Product Version: 3.0.12  
Product Build: 3.0.12 Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 3.0.13  
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?
Steps To Reproduce:
Additional Information:
Relationships
Attached Files:

Notes
(0000069)
ferg   
03-30-05 00:00   
server/269h

Configuration looks like:

<servlet servlet-class="com.caucho.servlets.HmuxLoadBalanceServlet">
  <init>
     <cluster>a</cluster>
     <strategy>load-balance</strategy>
  </init>
</servlet>
(0000070)
sam   
03-30-05 00:00   
Actually, configuration for round-robin looks like:

<servlet servlet-class="com.caucho.servlets.HmuxLoadBalanceServlet">
  <init>
     <cluster>a</cluster>
     <strategy>round-robin</strategy>
  </init>
</servlet>

Configuration for least-connection (the default) looks like:

<servlet servlet-class="com.caucho.servlets.HmuxLoadBalanceServlet">
  <init>
     <cluster>a</cluster>
     <strategy>least-connection</strategy>
  </init>
</servlet>

Documentation for the LoadBalanceServlet has been updated.