|Anonymous | Login | Signup for a new account||12-12-2019 19:11 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|
|0003055||[Resin]||minor||always||11-07-08 14:46||07-22-11 14:04|
|Summary||0003055: clustered config file restart enhancements|
(rep by Mark Morgan)
When resin finds a new copy of the config file, it restarts, which is great, but...I'd suggest that the servers in a cluster cooperate as to restarts, such that the placement of a new copy on all of them at once (or on shared storage) doesn't take a cluster out entirely. If they staggered such that the restart was a rolling matter, instead of simultaneous, it'd make things a lot more stable.
In this case, Resin 4.0.20 allows a combination of the command-line deploy with "manual" mode and then a command-line restart.
The deploy can be timed with a script.
|11-07-08 14:46||ferg||New Issue|
|07-22-11 14:04||ferg||Note Added: 0005390|
|07-22-11 14:04||ferg||Assigned To||=> ferg|
|07-22-11 14:04||ferg||Status||new => closed|
|07-22-11 14:04||ferg||Resolution||open => fixed|
|07-22-11 14:04||ferg||Fixed in Version||=> 4.0.20|
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed.|
25 unique queries executed.