[
https://issues.apache.org/jira/browse/TC-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Durfey updated TC-368:
---------------------------
Labels: api_deliveryservices routing (was: routing)
Summary: api/1.2/deliveryservices/:id/routing.json hangs when Traffic
Router is unreachable (was: /api/1.2/deliveryservices/:id/routing.json hangs
when Traffic Router is unreachable)
> api/1.2/deliveryservices/:id/routing.json hangs when Traffic Router is
> unreachable
> ----------------------------------------------------------------------------------
>
> Key: TC-368
> URL: https://issues.apache.org/jira/browse/TC-368
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops API
> Affects Versions: 1.8.0
> Reporter: Steve Malenfant
> Labels: api_deliveryservices, routing
>
> I was testing this API "/api/1.2/deliveryservices/:id/routing.json" and found
> that it would hang and the perl worker had to be killled. This caused 500
> Errors back from TO API.
> The root cause is Traffic Router not responding to API Port.
> We should not poll Traffic Router that are status=OFFLINE and there should be
> some sort of timeouts in place to make sure it doesn't take more than x
> seconds to return information from API
> There is some comments in the code that seems to indication prior issues.
> `# TODO: what happens when the request to CCR times out?`
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)