We keep track of the LastRetryAfter value in load_balanced.py. When no backends are available, and the last attempted backend possibly has a high retryAfter value, we would wait more than we need to as other backends may have become available again.
What I believe we should do then is return the nearest upcoming retry_after datetime property in the backends collection. The spec allows for either a datetime or seconds. I expect the httpx client to honor both.
simonkurtz-MSFT
commented
6 months ago
We keep track of the
LastRetryAftervalue inload_balanced.py. When no backends are available, and the last attempted backend possibly has a highretryAftervalue, we would wait more than we need to as other backends may have become available again.What I believe we should do then is return the nearest upcoming
retry_afterdatetime property in the backends collection. The spec allows for either a datetime or seconds. I expect the httpx client to honor both.