1. I wanted to limit the scope of this ticket to only detect disk failures in
initialization.2. I haven't verified that individual plugins can override the
proxy.config.http.cache.http but assuming that is true maybe we can allow this
exception since we cannot check run time plugin requirements at startup?
pushkar
On Monday, August 24, 2015 5:26 PM, sudheerv <g...@git.apache.org> wrote:
Github user sudheerv commented on the pull request:
https://github.com/apache/trafficserver/pull/280#issuecomment-134423458
Some questions/comments:
1) What happens when one or more disks fail during run time? The setting
name *proxy.config.http.cache.required* seems too confusing/restrictive that it
only applies to initialization.
2) Discussions on the IRC seem to indicate the
*proxy.config.http.cache.http* should not be used to indicate whether or not
cache is enabled. In particular, it is possible today to have
*proxy.config.http.cache.http* disabled globally, but, still have cache
initialized (allowing plugins to override *proxy.config.http.cache.http* for
individual transactions). So, using *proxy.config.http.cache.http = 0* to
ignore *proxy.config.http.cache.required* doesn't look correct and is not
compatible.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
