You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/06/14 19:15:27 UTC
[jira] [Commented] (TS-4536) hostdb serve_stale_for records
sometimes never expire
[ https://issues.apache.org/jira/browse/TS-4536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15330206#comment-15330206 ]
ASF GitHub Bot commented on TS-4536:
------------------------------------
GitHub user jacksontj opened a pull request:
https://github.com/apache/trafficserver/pull/713
TS-4536 Don't always refresh an IP when serving stale
With this as it stands, if a record is configured to serve stale the "creation" timeout keeps getting moved. This means if requests are made every second a record would NEVER expire-- which isn't what we want.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jacksontj/trafficserver TS-4536
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/713.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 #713
----
commit 34a6a5650de67cafdd252614e4ec14918500d150
Author: Thomas Jackson <ja...@gmail.com>
Date: 2016-06-14T19:14:36Z
TS-4536 Don't always refresh an IP when serving stale
With this as it stands, if a record is configured to serve stale the "creation" timeout keeps getting moved. This means if requests are made every second a record would NEVER expire-- which isn't what we want.
----
> hostdb serve_stale_for records sometimes never expire
> -----------------------------------------------------
>
> Key: TS-4536
> URL: https://issues.apache.org/jira/browse/TS-4536
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Thomas Jackson
> Assignee: Thomas Jackson
> Fix For: 7.0.0
>
>
> In hostdb when a record is served stale while revalidated-- the ip is refreshed. This means that hostdb sets the "query time" to when the record was served. In the extreme case, if a request comes in every second for the record it will NEVER expire-- which is presumably not what you want (nor what you configured).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)