[
https://issues.apache.org/jira/browse/TS-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Susan Hinrichs updated TS-1969:
-------------------------------
Fix Version/s: (was: 5.2.0)
sometime
> Mechanism to perform a graceful restart of trafficserver
> --------------------------------------------------------
>
> Key: TS-1969
> URL: https://issues.apache.org/jira/browse/TS-1969
> Project: Traffic Server
> Issue Type: New Feature
> Reporter: Kris Lindgren
> Assignee: Phil Sorber
> Labels: A, C
> Fix For: sometime
>
>
> For example HAproxy has the ability to start a new HAproxy instance to tell
> the old one to temporarily disconnect from the socket so the new process can
> take it over. If startup was successful then new connections are handled by
> the new HAproxy instance and old connections are handled by the old HAproxy
> instance. Once all the old connections have finished the old instance
> terminates.
> I am currently using 3.2.4 and am trying to mitigate the breaking of existing
> connections when restarting. Specifically around adding a new SSL cert, but
> It would also be nice to mitigate breaking of connections when changing
> listen ports as well, or when you change certain configurations options that
> require a restart. I understand that the current 3.3.x branch should have a
> feature to re-read the ssl certs without requiring a restart.
> One possible issue with the above model is that the cache could only be owned
> by one process. It would be nice if the old process would degrade into
> read-only or a proxy-only mode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
