[
https://issues.apache.org/jira/browse/TS-4929?focusedWorklogId=30182&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-30182
]
ASF GitHub Bot logged work on TS-4929:
--------------------------------------
Author: ASF GitHub Bot
Created on: 05/Oct/16 15:49
Start Date: 05/Oct/16 15:49
Worklog Time Spent: 10m
Work Description: Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1076
Yes, they would have TTLs, but if I turned off syncing, I certainly
wouldn't expect it to load something old. What if I had bad entries? What if I
had a corruption of some sort? Since it will never update it, you are stuck
with loading old (possibly stale or more likely expired) entries for the
remaining of life? That just makes no sense.
Issue Time Tracking
-------------------
Worklog Id: (was: 30182)
Time Spent: 50m (was: 40m)
> 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: 50m
> 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)
