Skip to content

U
unique-xids
Switch branch/tag
  1. 03 Feb, 2009 7 commits
  3. 02 Feb, 2009 1 commit
  5. 30 Jan, 2009 1 commit
  7. 28 Jan, 2009 3 commits
  9. 27 Jan, 2009 4 commits
  11. 24 Jan, 2009 2 commits
  13. 23 Jan, 2009 2 commits
  15. 22 Jan, 2009 2 commits
  17. 21 Jan, 2009 1 commit
    • Poul-Henning Kamp's avatar
      Enforce a minimum ttl for "hit for pass" objects to prevent a value · 99968684
      Poul-Henning Kamp authored 
      of zero from serializing access to an object with very draconian
backend cache-control headers.

We could get far even with a one second TTL, but following our general
"there is a reason people put Varnish there in the first place" logic
we use the default_ttl parameter (default: 120 s) for this value.

If another value is desired, this can be set in vcl_fetch, even if it
looks somewhat counter-intuitive:

	sub vcl_fetch {
		if (obj.http.set-cookie) {
			set obj.ttl = 10s;
			pass;
		}
	}

Fixes #425



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@3537 d4fa192b-c00b-0410-8231-f00ffab90ce4
      99968684
  19. 19 Jan, 2009 7 commits
  21. 18 Jan, 2009 9 commits
  23. 14 Jan, 2009 1 commit
    • Poul-Henning Kamp's avatar
      After HSH_Lookup() returns NULL indicating a busy object, we diddled · f50a3412
      Poul-Henning Kamp authored 
      the session a bit to transfer the per-request stats to the session
counters with SES_Charge().

Not only was it inconsistent to charge accounting data in the middle
of a request, it was also illegal because after the hash lock was
released we no longer owned the session.

Once a system is under sufficient load that there is a queue for the
CPU, a race could happen where upon hitting a busy object, the hash lock
was released, another thread would schedule, finish the busy object,
start the sessions on the waiting list, finish off the request we had
and then when we get the cpu again and access it, it's gone.

The previous commit (r3512) eliminated the need to call SES_Charge,
this commit removes the (option) shmlog message inside the hash lock
thus, hopefully, eliminating the race that caused #418.

Fixes: #418


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@3513 d4fa192b-c00b-0410-8231-f00ffab90ce4
      f50a3412