[jira] [Updated] (TS-2134) SRV lookup does not handle failover correctly
[ https://issues.apache.org/jira/browse/TS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2134: -- Fix Version/s: (was: 7.0.0) 7.1.0 > 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 >Assignee: Thomas Jackson > Labels: review > Fix For: 7.1.0 > > Attachments: ats.log, ts2134.patch > > > 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 was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-2134) SRV lookup does not handle failover correctly
[ https://issues.apache.org/jira/browse/TS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2134: -- Fix Version/s: (was: 6.2.0) 7.0.0 > 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 >Assignee: Thomas Jackson > Labels: review > Fix For: 7.0.0 > > Attachments: ats.log, ts2134.patch > > > 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 was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-2134) SRV lookup does not handle failover correctly
[ https://issues.apache.org/jira/browse/TS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2134: -- Assignee: Thomas Jackson (was: Alan M. Carroll) > 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 >Assignee: Thomas Jackson > Labels: review > Fix For: 7.0.0 > > Attachments: ats.log, ts2134.patch > > > 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 was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-2134) SRV lookup does not handle failover correctly
[ https://issues.apache.org/jira/browse/TS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan M. Carroll updated TS-2134: Fix Version/s: (was: 6.1.0) 6.2.0 > 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 >Assignee: Alan M. Carroll > Labels: review > Fix For: 6.2.0 > > Attachments: ats.log, ts2134.patch > > > 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 was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-2134) SRV lookup does not handle failover correctly
[ https://issues.apache.org/jira/browse/TS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-2134: Fix Version/s: (was: 6.0.0) 6.1.0 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 Assignee: Alan M. Carroll Labels: review Fix For: 6.1.0 Attachments: ats.log, ts2134.patch 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 was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-2134) SRV lookup does not handle failover correctly
[ https://issues.apache.org/jira/browse/TS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-2134: Fix Version/s: (was: 5.3.0) 6.0.0 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 Assignee: Alan M. Carroll Labels: review Fix For: 6.0.0 Attachments: ats.log, ts2134.patch 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 was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-2134) SRV lookup does not handle failover correctly
[ https://issues.apache.org/jira/browse/TS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susan Hinrichs updated TS-2134: --- Assignee: Alan M. Carroll 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 Assignee: Alan M. Carroll Labels: review Fix For: 5.3.0 Attachments: ats.log, ts2134.patch 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 was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-2134) SRV lookup does not handle failover correctly
[ https://issues.apache.org/jira/browse/TS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susan Hinrichs updated TS-2134: --- Fix Version/s: (was: 5.2.0) 5.3.0 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 Assignee: Alan M. Carroll Labels: review Fix For: 5.3.0 Attachments: ats.log, ts2134.patch 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 was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-2134) SRV lookup does not handle failover correctly
[ https://issues.apache.org/jira/browse/TS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan M. Carroll updated TS-2134: Fix Version/s: (was: 5.1.0) 5.2.0 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 Labels: review Fix For: 5.2.0 Attachments: ats.log, ts2134.patch 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 was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2134) SRV lookup does not handle failover correctly
[ https://issues.apache.org/jira/browse/TS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thach Tran updated TS-2134: --- Attachment: ts2134.patch I have been using this patch in our setup for some time and it seems to handle the SRV failover correctly as far as I can tell. Could someone help reviewing this since I'm not too sure on some of the details regarding how DNS SRV and hostdb are supposed to work in Traffic Server. 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 Fix For: sometime Attachments: ats.log, ts2134.patch 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 was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2134) SRV lookup does not handle failover correctly
[ https://issues.apache.org/jira/browse/TS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2134: -- Fix Version/s: (was: sometime) 5.1.0 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 Labels: review Fix For: 5.1.0 Attachments: ats.log, ts2134.patch 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 was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2134) SRV lookup does not handle failover correctly
[ https://issues.apache.org/jira/browse/TS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2134: -- Fix Version/s: 5.0.0 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 Fix For: 5.0.0 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
[jira] [Updated] (TS-2134) SRV lookup does not handle failover correctly
[ https://issues.apache.org/jira/browse/TS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thach Tran updated TS-2134: --- Attachment: ats.log debug log with http, dns, and hostdb tags enabled. 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
