Mantis - Resin
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1057 feature always 04-18-06 09:34 07-12-06 09:54
Reporter: sam Platform:  
Assigned To: ferg OS:  
Priority: normal OS Version:  
Status: closed Product Version: 3.0.19  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 3.0.20  
Summary: 0001057: shutdown-wait-strategy
Description: <shutdown-wait-strategy>request</shutdown-wait-strategy>

  start rejecting all new conenctions with a 503, allow currently
  active connections to finish, for the maximum time specified with shutdown-wait-max.

<shutdown-wait-strategy>session</shutdown-wait-strategy>

  start rejecting all conenctions without a session with a 503, allow connections with a session,
  for the maximum time specified with shutdown-wait-max.

For the second case, mod_caucho and the LoadBalanceServlet would need a dead-time of 0 or the presence of a special signal from the backend indicating that the server is not dead for requests with a session.
Steps To Reproduce:
Additional Information:
Relationships
Attached Files:

Notes
(0001308)
sam   
06-26-06 13:48   
Since there is already startup-mode, and redeploy-mode, it should be named
shutdown-mode:

<shutdown-mode>session</shutdown-mode>
<shutdown-mode>request</shutdown-mode>
<shutdown-mode>immediate</shutdown-mode>

New applications could automatically roll across the cluster with the addition of a shutdown-wait-start:
(session-timeout * (cluster-index % 8))
(0001373)
ferg   
07-06-06 16:19   
Add control item to LoadBalanceServlet to only let old sessions through.

So add this logic to the front-end, not the backend.
(0001383)
ferg   
07-12-06 09:54   
implemented by enableSessionOnly() on the load balancer.