Nick,
Yes, it happens on the same continuation. If there is a connection cannot
be opened to the upstream endpoint, the parent is marked down and the next
available parent on the consistent hash ring is then tried (no rehashing,
just next available).
Now when we say marked down, there is a thres
proxy.retry_time" setting.
>
> Thanks,
> Peter
>
> From: Nick Dunkin
> Sent: Tuesday, August 17, 2021 8:40 AM
> To: dev@trafficserver.apache.org
> Subject: Question about Consistent Hash and parent retry
>
> Hi,
>
> I have a
nfigurable using the "proxy.config.http.parent_proxy.retry_time"
setting.
Thanks,
Peter
From: Nick Dunkin
Sent: Tuesday, August 17, 2021 8:40 AM
To: dev@trafficserver.apache.org
Subject: Question about Consistent Hash and parent retry
Hi,
I have a question
g.
Thanks,
Peter
From: Nick Dunkin
Sent: Tuesday, August 17, 2021 8:40 AM
To: dev@trafficserver.apache.org
Subject: Question about Consistent Hash and parent retry
Hi,
I have a question about Consistent Hash behavior when a parent is “down”. This
is ATS 7.1
The documentation states the foll
> Please can someone clarify the exact behavior around Consistent Hash and
unavailable parents?
It's not a background thread. It's the same thread/continuation of a
regular request, but not every request, only after records.config
proxy.config.http.parent_proxy.retry_time. It will make either
pare
Hi,
I have a question about Consistent Hash behavior when a parent is “down”. This
is ATS 7.1
The documentation states the following: “If a parent is down, the traffic that
would go to the down parent is rehashed amongst the remaining parents. The
other traffic is unaffected. Once the downed