[
https://issues.apache.org/jira/browse/TS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725690#comment-14725690
]
ASF GitHub Bot commented on TS-3848:
------------------------------------
Github user SolidWallOfCode commented on the pull request:
https://github.com/apache/trafficserver/pull/282#issuecomment-136795398
Talked with @jpeach and he says this should be testable with multiple file
system cache spans. You need to either use multiple distinct directories or use
pre-allocated files. The easiest way to do the latter is first run with the
default file system cache setup, shut down, copy the cache file created to
different named files, then use those in `storage.config`.
> 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 the cache (none of the disks were accessible), the
> behavior depends on proxy.config.http.wait_for_cache:
> If wait_for_cache = 0, it will listen for requests and serve the requests (by
> fetching from origin/parent/peer).
> If wait_for_cache = 1, it will never listen for requests. This is almost like
> a hang.
> We would like to change this so that we can take some action when the cache
> fails to initialize (even partially):
> 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.
> Preconditions for this new behavior are:
> proxy.config.http.cache.required = 1 (HTTP caching enabled) and
> proxy.config.http.wait_for_cache = 1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
