codesite-noreply at google
Aug 4, 2008, 5:03 AM
Post #1 of 3
(253 views)
Permalink
|
|
Issue 81 in cherokee: Keep current existing connections while updating/upgrading the cherokee instance
|
|
Issue 81: Keep current existing connections while updating/upgrading
the cherokee instance
http://code.google.com/p/cherokee/issues/detail?id=81
New issue report by tahers:
It would be a nice to have.
Currently if changes made through cherokee-admin are applied, the instance
of cherokee is reinitiated loosing the whole queue of active connections.
We could implement a mechanism to allow launching a new instance of
cherokee with new configuration settings while and older one kept running
in parallel without accepting new connections. It should die once the queue
has been consumed. This would guarantee zero downtime.
In cherokee-admin this should translate as having some sort of checkbox
that allowed to keep at will the existing connections. It has to be
optional since sometimes it will be interesting just to kill everything.
This mechanism would also allow us to perform binary upgrades on the fly.
Issue attributes:
Status: Accepted
Owner: ----
Labels: Type-Enhancement Priority-Low
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
|
