[
https://issues.apache.org/jira/browse/TS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pushkar Pradhan updated TS-3848:
--------------------------------
Description:
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.
was:
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.
> 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)
