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
> Just to be clear for me. Is it correct to say that there is no
difference in the "parent mark down" behavior between Consistent Hash and
any of the other parent selection options (e.g. Round Robin)?
Correct. How it marks down and retries isn't related to the selection
algorithm. All those setti
Thanks Peter and Robert for all the input. Very useful information.
Just to be clear for me. Is it correct to say that there is no difference in
the "parent mark down" behavior between Consistent Hash and any of the other
parent selection options (e.g. Round Robin)?
Cheers,
Nick
On 8/17/21
Hi,
There is no background thread checking on the original parent. Once the
original parent is marked down, the parent selection process will ignore
it until it becomes retryable after a time-out period.
This is configurable using the "proxy.config.http.parent_proxy.retry_time"
setting.
Thanks,
> 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
