[
https://issues.apache.org/jira/browse/TS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758072#comment-13758072
]
Leif Hedstrom commented on TS-2134:
-----------------------------------
Does anyone at Alibaba/Taobao want to take this?
> SRV lookup does not handle failover correctly
> ---------------------------------------------
>
> Key: TS-2134
> URL: https://issues.apache.org/jira/browse/TS-2134
> Project: Traffic Server
> Issue Type: Bug
> Components: DNS, HTTP
> Reporter: Thach Tran
> Attachments: ats.log
>
>
> I'm seeing an issue with SRV lookup in ATS in which the proxy doesn't fail
> over to alternative origins once the first choice is marked as down.
> To reproduce this, I'm running dnsmasq as a local resolver to serve up the
> test SRV records. My configuration is as follows.
> h4. records.config
> CONFIG proxy.config.dns.nameservers STRING 127.0.0.1
> CONFIG proxy.config.dns.resolv_conf STRING NULL
> CONFIG proxy.config.srv_enabled INT 1
> h4. remap.config
> regex_remap http://.*:8080/ https://noexample.com/
> h4. dnsmasq.conf (srv records config)
> srv-host=_http._tcp.noexample.com,abc.com,443,0,100
> srv-host=_http._tcp.noexample.com,google.com,443,1,100
> The intention is since the srv lookup for _http._tcp.noexample.com returns
> abc.com:443 and google.com:443 with abc.com:443 being the one with higher
> priority, the proxy should try that first and once the connection to
> abc.com:443 is marked as down (up to 6 retries by default), google.com:443
> should be tried next and the connection should succeed then.
> However, testing with the following curl command multiple times still gives
> back 502.
> $ curl -v http://localhost:8080/
> Debug log seems to suggest it always attempts abc.com:443.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
