[
https://issues.apache.org/jira/browse/TS-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334113#comment-14334113
]
Adam W. Dace commented on TS-3118:
----------------------------------
Oh that's easy. Where I worked we had something called a RedLine(hardware
load-balancer) providing
both load-balancing and SSL compression.
Basically, any load-balancer worth its weight can handle this sort of thing.
That was my impression, anyways.
The load-balancer itself is responsible for knowing and managing the difference
between a new connection,
and an existing connection. Ideally, you'd want all existing connections
serviced properly, right?
Typically, the load-balancer(with some configuration) will handle this.
That being the case, the application itself is responsible for handling any
outstanding connections.
And to handle those connection without error. That's where the coding
difficulty comes in.
> 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)
