[
https://issues.apache.org/jira/browse/TS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711954#comment-14711954
]
Leif Hedstrom commented on TS-3848:
-----------------------------------
I disagree. I think wait_for_cache=1 and storage.config being empty is an error
case, and we should *at least* give serious Error()'s and/or Warning()'s on it.
My preference would be to exit() with an error code.
For example, we have had cases where a bad config push pushes an empty
storage.config. It'd be much better (in our case) to honor the wait_for_cache=1
and not let it proxy (because those boxes *would* kill the origin).
> ATS runs without cache or partial cache on disk errors
> ------------------------------------------------------
>
> Key: TS-3848
> URL: https://issues.apache.org/jira/browse/TS-3848
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache
> Reporter: Pushkar Pradhan
> Assignee: Alan M. Carroll
> Fix For: 6.1.0
>
>
> Problem:
> If ATS fails to initialize one or more disks it continues to run without
> cache. This can cause origin overload.
> The situation can be somewhat mitigated by setting
> proxy.config.http.wait_for_cache = 1 and if none of the disks failed to
> initialize.
> However, even if wait_for_cache = 1 and only one or a few disks failed to
> initialize, ATS will continue to serve traffic.
> Proposed Solution:
> Define a new variable: proxy.config.http.cache.required
> Value range: 0-2
> 0 (default) - Do nothing
> 1 - Abort trafficserver if it failed to initialize all the disks/volumes
> 2 - Abort trafficserver if it failed to initialize even one of the disks or
> volumes.
> If proxy.config.http.cache.required = 1 and proxy.config.http.wait_for_cache
> = 1 and if proxy.config.http.cache.required > 0 then abort the traffic server
> if one or more cache disks/volumes could not be initialized.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
