Updated Branches: refs/heads/master 425ceaf96 -> 17f782e7b
Thundering herd section-- background fill description error Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/commit/23839ca3 Tree: http://git-wip-us.apache.org/repos/asf/trafficserver/tree/23839ca3 Diff: http://git-wip-us.apache.org/repos/asf/trafficserver/diff/23839ca3 Branch: refs/heads/master Commit: 23839ca386dd0508b911a7b26824ac23b02b9987 Parents: 425ceaf Author: Miles Libbey <[email protected]> Authored: Wed Oct 9 14:21:22 2013 -0700 Committer: Miles Libbey <[email protected]> Committed: Wed Oct 9 14:21:22 2013 -0700 ---------------------------------------------------------------------- doc/admin/http-proxy-caching.en.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/trafficserver/blob/23839ca3/doc/admin/http-proxy-caching.en.rst ---------------------------------------------------------------------- diff --git a/doc/admin/http-proxy-caching.en.rst b/doc/admin/http-proxy-caching.en.rst index 1be97d9..42ef6c4 100644 --- a/doc/admin/http-proxy-caching.en.rst +++ b/doc/admin/http-proxy-caching.en.rst @@ -794,7 +794,7 @@ The configurations necessary to enable this in ATS are: All four configurations are required, for the following reasons: - enable_read_while_writer turns the feature on. It's off (0) by default -- The background fill feature should be allowed to kick in for every possible request. This is necessary, in case the writer ("first client session") goes away, someone needs to take over the session. The original client's request can go away after background_fill_active_timeout seconds, and the object will continue fetching in the background. The object then can start being served to another request after background_fill_completed_threshold % of the object has been fetched from origin. +- The background fill feature should be allowed to kick in for every possible request. This is necessary, in case the writer ("first client session") goes away, someone needs to take over the session. Hence, you should set the background fill timeouts and threshold to zero; this assures they never times out and always is allowed to kick in. - The proxy.config.cache.max_doc_size should be unlimited (set to 0), since the object size may be unknown, and going over this limit would cause a disconnect on the objects being served. Once all this enabled, you have something that is very close, but not quite the same, as Squid's Collapsed Forwarding.
