GitHub user jacksontj opened a pull request:
https://github.com/apache/trafficserver/pull/609
TS-4403: Fix stale-while-revalidate on DNS lookup failures
HostDB's "stale-while-revalidate" feature allows hostdb to return stale
records while doing the DNS lookup in the background. This works properly in
the case where the resolver goes away, but in the case that an error was
returned from the resolver the record in cache was thrown away. This means that
a transient error out in the DNS infrastructure would cause ATS to drop its
stale record it would have contently served-- this patch simply makes hostdb
honor its stale-while-revalidate contract (if configured). So, in the event
that the DNS result comes back as `failed` hostdb will keep the old one if it
is okay with being served stale.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jacksontj/trafficserver TS-4403
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/609.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #609
----
commit 92bba349b5e4846761245e4629921632355c3c83
Author: Thomas Jackson <jacksontj...@gmail.com>
Date: 2016-04-30T19:16:40Z
TS-4403: Fix stale-while-revalidate on DNS lookup failures
HostDB's "stale-while-revalidate" feature allows hostdb to return stale
records while doing the DNS lookup in the background. This works properly in
the case where the resolver goes away, but in the case that an error was
returned from the resolver the record in cache was thrown away. This means that
a transient error out in the DNS infrastructure would cause ATS to drop its
stale record it would have contently served-- this patch simply makes hostdb
honor its stale-while-revalidate contract (if configured). So, in the event
that the DNS result comes back as `failed` hostdb will keep the old one if it
is okay with being served stale.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
