[
https://issues.apache.org/jira/browse/TS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711696#comment-14711696
]
Leif Hedstrom commented on TS-3848:
-----------------------------------
Going back reading this, from the beginning. The statement is
"If ATS fails to initialize one or more disks it continues to run without
cache. This can cause origin overload."
is that really the case? If it is, it's a major (catastrophic) regression, that
should be addressed. Adding more features does not seem like the right solution
to that original problem statement.
Now, I'm not opposed to new knobs and whistles, but lets make sure we solve the
right problems first.
> 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)
