[
https://issues.apache.org/jira/browse/TS-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711590#comment-14711590
]
Sudheer Vinukonda commented on TS-3837:
---------------------------------------
Perhaps, you are probably indicating that this is a configuration error and
should be left alone? Hmm, Unless you are very strongly opposed to it, I would
rather log an error/warning and simply ignore the *wait_for_cache* setting when
cache is not configured. IMO, this is one of those configuration "mistakes"
that can be tolerated, but, I'm fine with the general consensus.
> 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)
