Updating from 2.0.5 to 3.0.0 - some questions
Lee Trout
lee at leetrout.com
Sat Feb 18 05:44:56 CET 2012
Jim,
Make sure you adjust the new run time http_req_hdr_len
and http_resp_hdr_len if you're site (or clients) send large headers. We
discovered that our headers were averaging 8-12kb which is 2-3x the default
4096 bytes.
That was a tricky one for us to sort out since only certain clients had the
large cookie headers and the 413 errors were intermittent in varnishlog.
Lee
2012/2/17 kokoniimasu <kokoniimasu at gmail.com>
> Hi Jim,
>
> you're working varnish is 2.0.5? 2.1.5?
>
> if varnish is 2.0.X. refer to this url.(sorry Japanese. but I put an
> English comment)
>
>
> http://wiki.xcir.net/index.php?title=Versuin2.0.x%E2%86%922.1.x%E3%81%B8%E3%81%AEVUP
>
> --
> Syohei Tanaka(@xcir)
> http://xcir.net/
>
> (:3[__])
>
>
> 2012年2月18日2:37 Jim Hayter <jim.hayter at gmail.com>:
> > I am working on upgrading from Varnish 2.0.5 running on Ubuntu 9.10 to
> > Varnish 3.0.0 running on Ubuntu 11.10.
> >
> > I have a few questions based on my reading of
> > https://www.varnish-cache.org/trac/browser/doc/changes.rst
> >
> > 1) Changes from 2.1.5 to 3.0 beta 1 states:
> >
> > - The -l (shared memory log file) argument has been changed, please
> > see the varnishd manual for the new syntax.
> > 'man varnishd' for 2.0.5 states:
> >
> > -l shmlogsize
> > Specify size of shmlog file. Scaling suffixes like 'k',
> 'm'
> > can be used up to (e)tabytes. Default is 80 Megabytes.
> > Specifying less than 8 Megabytes is unwise.
> >
> > 'man varnishd' for 3.0.0 states the same thing. And it appears to
> > be working. What changed?
> >
> >
> > 2) I'm also a bit confused by this code in vcl_fetch:
> >
> > if (beresp.ttl <= 0s ||
> > beresp.http.Set-Cookie ||
> > beresp.http.Vary == "*") {
> > /*
> > * Mark as "Hit-For-Pass" for the next 2 minutes
> > */
> > set beresp.ttl = 120 s;
> > return (hit_for_pass);
> > }
> >
> > What is the purpose of "set beresp.ttl = 120 s;" ? So, the
> > purpose is to mark as "Hit-For-Pass" for 2 minutes, but why is this
> > done (what does it accomplish)?
> >
> > 3) I've noted that a number of the parameter values I used to set have
> > become defaults. I also noted the change to make thread_pool_min and
> > thread_pool_max agree better. Aside from these and some other changes
> > (purge to ban, obj to beresp), are there particular changes I should
> > look at closely to avoid problems when I update?
> >
> > 4) Is there additional doc I should review (besides
> > https://www.varnish-cache.org/trac/browser/doc/changes.rst) that would
> > help me avoid problems and understand what has changed?
> >
> > Thanks for any suggestions.
> >
> > Jim
> >
> > _______________________________________________
> > varnish-misc mailing list
> > varnish-misc at varnish-cache.org
> > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20120217/114f64f1/attachment-0001.html>
More information about the varnish-misc
mailing list