[
https://issues.apache.org/jira/browse/TS-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208745#comment-14208745
]
Peter Walsh commented on TS-2573:
---------------------------------
It has been awhile since I looked into it, but I recall there was a 5 second
timeout when peer fetching. It was not configurable (that I recall). Once a
particular node in the cluster entered this "bad state", we saw continual
timeouts with peer fetching until it was restarted.
But since this is not a concern at this point, I'd say go ahead and close it.
I can reopen if necessary. I last saw it on 4.0.1 so I am not even sure if the
bug is still in the current code base.
> Exponentional increasing of cluster timeouts
> --------------------------------------------
>
> Key: TS-2573
> URL: https://issues.apache.org/jira/browse/TS-2573
> Project: Traffic Server
> Issue Type: Bug
> Components: Clustering
> Reporter: Peter Walsh
> Fix For: sometime
>
>
> Occasionally we see cluster operations will start timing out after 5 seconds.
> This will continue at an increasing rate until traffic server is restarted.
> The following stats increase when this happens,
> proxy.process.cluster.remote_op_timeouts and
> proxy.process.cluster.connections_open.
> I can tell that spikes in IO wait can contribute to this issue.
> Any ideas?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
