[
https://issues.apache.org/jira/browse/TS-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15316783#comment-15316783
]
Thomas Jackson commented on TS-4436:
------------------------------------
[~psudaemon] This is a bugfix-- although it does mean that there is a slight
behavior change-- although from talking to people the change is to what people
expected.
The TLDR is that the old hosts file mechanism would incorrectly track "down"
reals-- meaning that if you had "origins" that used an origin (lets say
localhost:12345 and localhost:54321) they would both use the same record--
meaning a failure of one would cause ATS to not attempt talking to either.
So, although a change in behavior-- I definitely see it as a bugfix.
> ATS' tracking of host failures is broken for entries acquired through the
> hosts file
> ------------------------------------------------------------------------------------
>
> Key: TS-4436
> URL: https://issues.apache.org/jira/browse/TS-4436
> Project: Traffic Server
> Issue Type: Bug
> Components: HostDB
> Reporter: Thomas Jackson
> Assignee: Thomas Jackson
> Fix For: 7.0.0
>
>
> The current implementation of the hosts file maintains a map of name to
> hostdbinfo, which means that any lookups that come into the probe method
> return the same hostdbinfo struct. This means that any requests to a given
> address (regardless of port) recieve the same HostDBInfo struct-- which in
> turn means that the up/down status is global to the IP instead of per ip/port
> pair.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
