New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 845144 link

Starred by 2 users
Status: Fixed
Owner:
pauljensen@chromium.org
Closed: Aug 30
Cc:
pauljensen@chromium.org
█ mdumitrescu@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

[Cronet] Stale Host resolver has increased number of NXDOMAIN errors

Project Member Reported by mef@chromium.org, May 21 2018 
See internal b/29525886 for details.

The stale host resolver experiment increases number of NAME_NOT_RESOLVED instead of reducing them. 

Strangely those errors are returned within 4-10ms, suggesting that they don't hit the network.

We should add an experimental flag to allow use of stale results if NXDOMAIN is returned from system dns resolver.

Comment 1 by mef@chromium.org, May 21 2018 

Looking at the code we should be able to modify StaleHostResolver::RequestImpl::OnNetworkRequestComplete() to return stale results if network request completes with non-Ok.

This should be controlled by the flag as overall effect is not quite clear (we still don't understand the source of quick 4-10ms failures).

Comment 2 by mef@chromium.org, Aug 30

Owner: pauljensen@chromium.org
Status: Fixed (was: Untriaged)
This is fixed by Pauls CL https://chromium-review.googlesource.com/c/chromium/src/+/1179998
►

Sign in to add a comment