[
https://issues.apache.org/jira/browse/TS-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700183#comment-14700183
]
Sudheer Vinukonda commented on TS-3837:
---------------------------------------
AFAIK, there's no agreement (yet) on the aspect of exit'ing TS initialization
on failure to initialize any caches - Cache is an optional feature and failure
to initialize cache should not automatically fail TS from coming up, as long as
*wait_for_cache* is not enabled. When *wait_for_cache* is enabled, currently,
TS does not accept any incoming connections until the cache is initialized.
There's a plan to enhance this further as part of TS-3848.
Setting *proxy.config.http.cache.required* to *0* is not sufficient to let
cache not initialize - As long as, there's something configured in
*storage.config*, TS always initializes the cache (independent of
*proxy.config.http.cache.required*). This allows for plugins to override the
setting *proxy.config.http.cache.required* on an individual transaction basis,
despite disabling the setting globally.
At present, the only way to disable cache is by leaving *storage.config* empty
and the requirement on this Jira is only to ignore *wait_for_cache* setting
when *storage.config* is empty.
Also, just to clarify further, *ignore* here means, to allow TS to initialize
as a proxy-only and allow requests to be proxied without cache.
> The setting wait_for_cache waits indefinitely even when there are no cache
> disks configured.
> --------------------------------------------------------------------------------------------
>
> Key: TS-3837
> URL: https://issues.apache.org/jira/browse/TS-3837
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache, HTTP
> Affects Versions: 6.1.0
> Reporter: Sudheer Vinukonda
> Assignee: Alan M. Carroll
> Fix For: 6.1.0
>
>
> The setting *proxy.config.http.wait_for_cache* allows to let traffic_server
> wait for the cache to initialize before processing requests (it basically
> blocks accepts). This is fine when cache is configured, but, if there are no
> disks configured in *storage.config*, this setting makes requests wait
> indefinitely. Ideally, the setting should consider cache initialized
> (disabled) when no disks are configured and just proxy the requests rather
> than block them forever.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
