Mailing List Archive: Varnish: Misc

Updating from 2.0.5 to 3.0.0 - some questions

Index | Next | Previous | View Threaded

jim.hayter at gmail

Feb 17, 2012, 9:37 AM

Post #1 of 5 (347 views)
Permalink

Updating from 2.0.5 to 3.0.0 - some questions

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
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc

kokoniimasu at gmail

Feb 17, 2012, 7:48 PM

Post #2 of 5 (315 views)
Permalink

Re: Updating from 2.0.5 to 3.0.0 - some questions [In reply to]

Hi Jim,

>1) Changes from 2.1.5 to 3.0 beta 1 states:

[root [at] localhos ~]# varnishd
At least one of -d, -b, -f, -M, -S or -T must be specified
usage: varnishd [options]

...

-l shl,free,fill # Size of shared memory file
# shl: space for SHL records [80m]
# free: space for other allocations [1m]
# fill: prefill new file [+]

>2) I'm also a bit confused by this code in vcl_fetch:

Refer to this url.
https://www.varnish-cache.org/docs/trunk/faq/general.html#troubleshooting

>3) I've noted that a number of the parameter values I used to set have

If varnish's change parameter you want to know? (I'm sorry if I get it
wrong. I'm not good at English... training now)
This document may be relevant to you.
http://blog.xcir.net/index.php/2011/07/vcl-and-parameter-changes-in-varnish-cache-3-0/

http_req_hdr_len is require special care.(if you wants very large
request header(~2kb))

>4) Is there additional doc I should review (besides

Refer to this url.
https://www.varnish-cache.org/docs/trunk/installation/upgrade.html

I hope you find it informative.

--
Syohei Tanaka(@xcir)
http://xcir.net/

(:3[__])

2012$BG/(B2$B7n(B18$BF|(B2:37 Jim Hayter <jim.hayter [at] gmail>:
> 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
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc

_______________________________________________
varnish-misc mailing list
varnish-misc [at] varnish-cache
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc

kokoniimasu at gmail

Feb 17, 2012, 8:21 PM

Post #3 of 5 (331 views)
Permalink

Re: Updating from 2.0.5 to 3.0.0 - some questions [In reply to]

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$BG/(B2$B7n(B18$BF|(B2:37 Jim Hayter <jim.hayter [at] gmail>:
> 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
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc

_______________________________________________
varnish-misc mailing list
varnish-misc [at] varnish-cache
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc

lee at leetrout

Feb 17, 2012, 8:44 PM

Post #4 of 5 (316 views)
Permalink

Re: Updating from 2.0.5 to 3.0.0 - some questions [In reply to]

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>

> 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>:
> > 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
> > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc [at] varnish-cache
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>

jim.hayter at gmail

Feb 20, 2012, 9:14 AM

Post #5 of 5 (302 views)
Permalink

Re: Updating from 2.0.5 to 3.0.0 - some questions [In reply to]

Thank you both for your responses.

The list of parameter and syntax changes at xcir.net were very helpful.

Lee, I appreciate the warning about the headers. I was already
worried about that as I had to build 2.0.5 with
'--with-max-header-fields=200' due to the amount of headers our pages
sometimes use.

Thanks again,
Jim

On Fri, Feb 17, 2012 at 11:44 PM, Lee Trout <lee [at] leetrout> wrote:
> 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>
>>
>> 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>:
>> > 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
>> > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>>
>> _______________________________________________
>> varnish-misc mailing list
>> varnish-misc [at] varnish-cache
>> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
>

_______________________________________________
varnish-misc mailing list
varnish-misc [at] varnish-cache
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads