[ https://issues.apache.org/jira/browse/TS-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333641#comment-14333641 ]
James Peach commented on TS-3118: --------------------------------- There's already a mechanism to automatically delay a restart until the number of client sessions drops below a configured threshold. It would not be that hard to extend this to stop accepting new connections. However, typically there is a layer above that is draining connections (ie. some balancing infrastructure), so implementing this behavior would imply serving errors to clients, which is probably not desirable. If we published the "shutting down" state as a metric, then it would be possible to write a plugin to take appropriate action. Options could be serving the request, dropping the client, serving a HTTP redirect, etc. > Feature to stop accepting new connections > ----------------------------------------- > > Key: TS-3118 > URL: https://issues.apache.org/jira/browse/TS-3118 > Project: Traffic Server > Issue Type: New Feature > Reporter: Miles Libbey > Labels: A > Fix For: 5.3.0 > > > When taking an ATS machine out of production, it would be nice to have ATS > stop accepting new connections without affecting the existing client > connections to minimize client disruption. -- This message was sent by Atlassian JIRA (v6.3.4#6332)