[
https://issues.apache.org/jira/browse/TS-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711577#comment-14711577
]
Sudheer Vinukonda commented on TS-3837:
---------------------------------------
There's indeed a "problem" with the current behavior, where ATS waits
regardless of whether or not cache is configured (when *wait_for_cache* is
enabled). When cache is not configured, this manifests as indefinite wait.
And the ticket does ask exactly what you are referring to as the "right"
solution - i.e. to tell ATS not to wait for cache when there's no cache
configured.
> 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)
