[
https://issues.apache.org/jira/browse/TS-4601?focusedWorklogId=26697&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26697
]
ASF GitHub Bot logged work on TS-4601:
--------------------------------------
Author: ASF GitHub Bot
Created on: 20/Aug/16 00:14
Start Date: 20/Aug/16 00:14
Worklog Time Spent: 10m
Work Description: Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/762
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/Github-Linux/460/ for details.
Issue Time Tracking
-------------------
Worklog Id: (was: 26697)
Time Spent: 40m (was: 0.5h)
> Connection error from origin_max_connection with origin_max_connections_queue
> set to 0 should not retry
> -------------------------------------------------------------------------------------------------------
>
> Key: TS-4601
> URL: https://issues.apache.org/jira/browse/TS-4601
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: Susan Hinrichs
> Assignee: Susan Hinrichs
> Fix For: 7.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> While adding a metric to track the number of times a connection to origin is
> dropped due to being over the origin_max_connections limit, I noticed that
> the count was increments three times as fast as I expected from my
> experiment. My connection retry count was 3. I changed the logic to set the
> current attempts to max to avoid the retries in that case.
> [~jacksontj] avoiding the retries makes sense in this case, right?
> I also propose adding a proxy.process.http.origin_connections_throttled
> metric to track how many connections to origin are being error'ed out the
> origin_max_connection limit. The metric is only incremented when the queue
> is 0 or we are over the delay queued limit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
