[
https://issues.apache.org/jira/browse/TS-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334093#comment-14334093
]
James Peach commented on TS-3118:
---------------------------------
In that scheme, what prevents clients receiving errors between steps (1) and
(2)?
I think there's a lot of variety in this sort of orchestration. The typical
workflow that I have seen is that the load balancer polls a HTTP endpoint. When
you take the server out of rotation, you arrange for the endpoint to return a
non-200 status. In this way, new client requests are still serviced until (2)
takes place.
> 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)
