[
https://issues.apache.org/jira/browse/TS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14717290#comment-14717290
]
ASF GitHub Bot commented on TS-3848:
------------------------------------
GitHub user pushkarpradhan opened a pull request:
https://github.com/apache/trafficserver/pull/282
This is the fix for TS-3848.
The values for wait_for_cache are extended to the range 0-3.
If none of the disks or volumes could be initialized and the wait_for_cache
value is 2, traffic_server will abort.
If even one or more of the disks or volumes could not be initialized
and the wait_for_cache value is 3, traffic_server will abort.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pushkarpradhan/trafficserver ts3848-2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/282.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #282
----
commit 7b9f36d78eea80ca0b2018b82e0fcbcbf0b6fbcb
Author: Pushkar Pradhan <pprad...@apache.org>
Date: 2015-08-17T22:54:05Z
This is the fix for TS-3848.
The values for wait_for_cache are extended to the range 0-3.
If none of the disks or volumes could be initialized and the wait_for_cache
value is 2, traffic_server will abort.
If even one or more of the disks or volumes could not be initialized
and the wait_for_cache value is 3, traffic_server will abort.
----
> 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)
