| Anonymous | Login | Signup for a new account | 06-10-2026 07:13 PDT |
| 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 | ||||
| 0004849 | [Resin] | feature | always | 11-10-11 08:55 | 06-11-12 15:25 | ||||
| Reporter | alex | View Status | public | ||||||
| Assigned To | ferg | ||||||||
| Priority | normal | Resolution | no change required | ||||||
| Status | closed | Product Version | 4.0.23 | ||||||
| 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> |
||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
Notes |
|
|
(0005821) ferg 06-11-12 15:25 |
This capability will not be addressed until we add the backwards/messaging proxy. |
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed. 26 unique queries executed. |