[
https://issues.apache.org/jira/browse/TS-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623540#comment-14623540
]
Alan M. Carroll commented on TS-1419:
-------------------------------------
I've changed the bug title because I don't think this has anything to do with
strict round robin, it is simply easier to detect in that case.
The basic problem is that the HttpSM wasn't detecting that the current address
was part of a round robin group and so did not fail over to another address in
that group.
> Round Robin Failover doesn't work
> ---------------------------------
>
> Key: TS-1419
> URL: https://issues.apache.org/jira/browse/TS-1419
> Project: Traffic Server
> Issue Type: Bug
> Components: DNS
> Affects Versions: 3.3.0, 3.2.0
> Environment: CONFIG proxy.config.hostdb.strict_round_robin INT 1
> Reporter: Bin Chen
> Assignee: Alan M. Carroll
> Labels: yahoo
> Fix For: 6.1.0
>
>
> in strict round robin mode, some hostdb entry marked down(ip is down) will be
> used, then some request will be responsed 502. Should we skip entry which be
> marked down? so, we can't always response by alive server(up entry).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
