|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 4849 | feature | always | 11-10-11 08:55 | 06-11-12 15:25 | |
|
|
|||||
| Reporter: | alex | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.23 | ||
| Product Build: | Resolution: | no change required | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
|
|
|||||
| Summary: | 0004849: load-balance update after applications loaded on a server | ||||
| Description: |
I have a problem with clustering in Resin 4.0.23 that I hope someone can help me with. When I bring a cluster node back online after it has been shut down the cluster recognizes it as "up and functioning" too soon (this can be monitored on the caucho-status page). My problem is that I have a servlet that is really heavy to start and it has <load-on-startup> set. As it is set up now requests goes to this new node trying to access the servlet prior too its startup and they are left waiting. I would like to have the cluster node off line until all the <load-on-startup> servlets has started. Is there an existing setting that can make this work? What I am looking for is something like <load-balance-grace-time> or <cluster-off-line-until-load-on-startup-done> |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||