[
https://issues.apache.org/jira/browse/TS-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705344#comment-14705344
]
Sudheer Vinukonda commented on TS-3837:
---------------------------------------
I am not sure if we should add any specific feature based settings (especially,
upstream), given that the direction seems to be towards a general solution for
this problem.
It seems like we should be able to address the immediate issue with the
*wait_for_cache* setting (if that can be fixed to return immediately when cache
is disabled (based on empty storage.config - NOT based on http.cache setting)
it'd be even better).
> 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)
