[jira] [Commented] (TS-3848) ATS runs without cache or partial cache on disk errors

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725646#comment-14725646 ] 

ASF GitHub Bot commented on TS-3848:
------------------------------------

Github user SolidWallOfCode commented on the pull request:

    https://github.com/apache/trafficserver/pull/282#issuecomment-136780619
  
    Testing results, empty `storage.config` and `wait_for_cache`
    
    0) ATS starts up with cache disabled. Cache lifecycle hook not called.
    1) ATS hangs (broken)
    2,3)  ATS fatal exits (correct). Cache lifecycle hook not called.
    
    `storage.config` with multiple drives, `wait_for_cache`
    0) ATS starts up with cache disabled. Lifecylce hook not called.
    1) ATS hangs.
    2) Run on partial drives available, fail on all drives unavailable (correct). Lifecycle hook not called if traffic_server terminates.
    3) Fail on all drives or some drives not available (correct). Lifecycle hook not called if traffic_server terminates.
      Fail: lifecycle hook for cache not called in fail to start case.


> 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)