Anonymous | Login | Signup for a new account | 11-21-2024 10:24 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 | |||||||
0006291 | [Resin] | minor | always | 10-21-19 05:07 | 03-21-24 07:10 | |||||||
Reporter | nam | View Status | public | |||||||||
Assigned To | ||||||||||||
Priority | high | Resolution | open | |||||||||
Status | new | Product Version | 4.0.62 | |||||||||
Summary | 0006291: mod_caucho does not see new elastic servers | |||||||||||
Description |
(rep by J. Meyer) mod_caucho does not automatically pick up new elastic servers. The elastic servers should show up under the virtual host section. The issue appears to Resin's failure to update the in-memory host etag cache after a cluster change. The workarounds are either: 1. restarting the triad servers, thereby clearing the cache on the backend, or 2. restarting apache/mod_caucho, thereby clearing the cache on the frontend If only a triad server is restarted, then mod_caucho would eventually see the elastic server when it queries the restarted triad server through round-robin. code trail: 1. HmuxDispatchRequest.handleRequest() 2. HmuxDispatchRequest.queryAll() 3. Host.setConfigETag() An alternative workaround is to prevent mod_caucho from sending the etag to Resin. In modules/c/src/common/config.c->cse_update_host_from_resin(), delete the following lines: if (host->etag[0]) hmux_write_string(&s, HMUX_DISPATCH_ETAG, host->etag); |
|||||||||||
Additional Information | ||||||||||||
Attached Files | among-us-shooting-boxes.jpg [^] (4,633 bytes) 03-21-24 07:10 | |||||||||||
|
There are no notes attached to this issue. |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
46 total queries executed. 31 unique queries executed. |