[
https://issues.apache.org/jira/browse/TS-4929?focusedWorklogId=30181&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-30181
]
ASF GitHub Bot logged work on TS-4929:
--------------------------------------
Author: ASF GitHub Bot
Created on: 05/Oct/16 15:26
Start Date: 05/Oct/16 15:26
Worklog Time Spent: 10m
Work Description: Github user jpeach commented on the issue:
https://github.com/apache/trafficserver/pull/1076
@zwoop (1) and (2) sound like they are in conflict? I'm confused about
whether it loads or not? If it does load, do you really have a stale record
problem, since each record has a TTL?
Issue Time Tracking
-------------------
Worklog Id: (was: 30181)
Time Spent: 40m (was: 0.5h)
> Should we avoid loading HostDB disk file is sync_frequency is '0' (disabled)
> ----------------------------------------------------------------------------
>
> Key: TS-4929
> URL: https://issues.apache.org/jira/browse/TS-4929
> Project: Traffic Server
> Issue Type: Improvement
> Components: HostDB
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Fix For: 7.1.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> This addresses two issues:
> 1) We get warnings trying to load a non-existent HostDB (since we don't sync
> it).
> 2) Worse, if someone has an old HostDB, that is no longer synced / updated,
> we load the old, possibly stale, data on every startup.
> #2 seems inconsistent with the other changes to HostDB, where now the sync
> frequency =0 truly turns off disk syncing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
