[
https://issues.apache.org/jira/browse/TS-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542560#comment-15542560
]
John Rushford commented on TS-4912:
-----------------------------------
I was testing parent selection using three tiers of proxy parent selection and
intially saw an increase in 502's but, it came down to adjusting the
proxy.config.http.parent_proxy.connect_attempts_timeout config. I had set this
to 5 seconds in both my edge and mid-tier caches and when disabling parents in
the third tier, I saw an increase in 502's. The 502's were caused because my
edge tier was closing the connection after the 5 second timeout while the
mid-tier was retrying the transaction using a new parent. After doubling
proxy.config.http.parent_proxy.connect_attempts_timeout to 10 seconds on my
fedge tier, the 502's stopped as there was now sufficient time for the 2nd
mi-d-tier to retry the connection using a new parent.
> Increase in 502 when upgrading from 6.1 to 6.2 with parent proxy
> ----------------------------------------------------------------
>
> Key: TS-4912
> URL: https://issues.apache.org/jira/browse/TS-4912
> Project: Traffic Server
> Issue Type: Bug
> Components: Parent Proxy
> Affects Versions: 6.2.0, 7.0.0
> Reporter: Leif Hedstrom
> Assignee: John Rushford
> Priority: Blocker
> Labels: A
> Fix For: 7.1.0
>
>
> After upgrading to 6.2.x, we started noticing significant increases in 502
> responses. We are using parent proxy heavily, so maybe this is related to
> parent selection and/or handling?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
