[Varnish] #1239: Problem with cleaning up "gone" bans
Varnish
varnish-bugs at varnish-cache.org
Wed Jan 9 10:15:10 CET 2013
#1239: Problem with cleaning up "gone" bans
----------------------+----------------------
Reporter: xani | Owner: martin
Type: defect | Status: closed
Priority: normal | Milestone:
Component: varnishd | Version: 3.0.3
Severity: normal | Resolution: invalid
Keywords: |
----------------------+----------------------
Changes (by martin):
* status: new => closed
* resolution: => invalid
Comment:
Hi,
Ban list length starting to accumulate when you have req.* parts in your
ban lists is very much the expected behavior. Due to the way ban lists are
implemented, they can only ever be removed off the tail of the list. The
ban lurker's responsibility is to work on the tail of the list in order to
free the bans there. But the moment a req.* ban is at the tail, the ban
lurker can't do anything with it (the ban lurker obviously is not running
in the context of a request, thus can't match anything on req.*). So the
ban list length then will grow indefinitely until that ban clears any
other way (objects it's linked to is actually requested or their TTL
elapses). Solution is to not use ban expressions with req.* in them.
I'll close this ticket as invalid.
Regards,
Martin Blix Grydeland
--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1239#comment:6>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator
More information about the varnish-bugs
mailing list