[
https://issues.apache.org/jira/browse/TS-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879297#comment-13879297
]
Alan M. Carroll commented on TS-1893:
-------------------------------------
Meh, I'm not going to worry about the external DNS round robin issue. I spent a
while thinking about it and it's (1) hard/expensive to detect and (2) is
limited by server connection lifetime anyway. Additional clients beyond the
existing set of sessions will go to the newly valid IP addresses.
> Make ATS use keep-alive connections per origin address
> ------------------------------------------------------
>
> Key: TS-1893
> URL: https://issues.apache.org/jira/browse/TS-1893
> Project: Traffic Server
> Issue Type: Improvement
> Components: HTTP, Network, Performance
> Reporter: Tomasz Kuzemko
> Assignee: Alan M. Carroll
> Fix For: 5.0.0
>
> Attachments: TS-1893-PoC.diff
>
>
> In current implementation Traffic Server uses a two level hash for keep-alive
> connections: server ip -> hostname -> keep-alive session.
> The reasoning behind this was that some old http servers could not handle the
> request properly for different virtual hosts on the same keep-alive session.
> Recent web servers should all handle this situation correctly.
> The improvement would be to make a single level hash to keep just the server
> ip. Shared hosting configurations using ATS as a reverse-proxy could benefit
> the most from this improvement.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
