This could bite some users when upgrading large installations. -- Andreas
>From d88d331d6d509b8365610d9fe3ba90c269569059 Mon Sep 17 00:00:00 2001 From: Andreas Plesner Jacobsen <[email protected]> Date: Tue, 16 Aug 2011 16:22:10 +0200 Subject: [PATCH 2/2] Add note about thread_pool_max
--- doc/sphinx/installation/upgrade.rst | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/doc/sphinx/installation/upgrade.rst b/doc/sphinx/installation/upgrade.rst index 1a31733..03720ac 100644 --- a/doc/sphinx/installation/upgrade.rst +++ b/doc/sphinx/installation/upgrade.rst @@ -110,3 +110,5 @@ Changes to behaviour ==================== Varnish will return an error when headers are too large instead of just ignoring them. If the limits are too low, Varnish will return HTTP 413. You can change the limits by increasing http_req_hdr_len and http_req_size. + +thread_pool_max is now per thread pool, while it was a total across all pools in 2.1. If you had this set in 2.1, you should adjust it for 3.0. -- 1.7.2.3
_______________________________________________ varnish-dev mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
