[
https://issues.apache.org/jira/browse/TS-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166446#comment-15166446
]
Leif Hedstrom commented on TS-4228:
-----------------------------------
Although this doesn't solve the problem with traffic_server. I will file
another Jira, tracking why the heck _server isn't proxying the request to
manager properly. We've seen this behavior before in 5.3.x as well (I *think*)
it's just that with the new manager code for this, it issues itself as
traffic_manager chewing up CPU badly.
> traffic_manager can hang in a tight read() loop
> ------------------------------------------------
>
> Key: TS-4228
> URL: https://issues.apache.org/jira/browse/TS-4228
> Project: Traffic Server
> Issue Type: Bug
> Components: Manager
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Fix For: 6.2.0
>
>
> Under certain conditions, traffic_server does not seem to proxy the cop
> health check properly to the traffic_manager. Due to poor error handling in
> the manager thread, this can cause it to run indefinitely in a read() loop.
> I think we should strengthen the code in manager, to check FD with a poll()
> before every read and write, and allow it to fail after a certain timeout
> (based on Cop's behavior) such that at least we end up killing the request
> and manager thread.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
