[
https://issues.apache.org/jira/browse/TS-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334078#comment-14334078
]
Adam W. Dace commented on TS-3118:
----------------------------------
Actually, having worked in such a shop, we usually handled this as such:
1) The application shuts down its listening connection.
2) Load-balancing hardware detects this and takes that server out of the active
pool(no errors).
3) Existing connections are serviced.
4) Once all existing connections have been completed, the application begins
actual shutdown.
My knowledge is a bit out of date...but this might be the behavior some are
looking for.
The upside is this enables all sorts of operational work that would otherwise
interrupt business.
There's nothing like shutting down an active application in the middle of the
workday(i.e. high load). :-)
P.S. I know this is painful to implement, from a code perspective, but
unfortunately attaining high availability isn't always easy.
> 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)
