[Varnish] #1083: Persistent Varnish crashes since using bans and lurker

[Varnish]

#1083: Persistent Varnish crashes since using bans and lurker
-------------------------+---------------------
 Reporter:  rmohrbacher  |       Owner:  martin
     Type:  defect       |      Status:  new
 Priority:  high         |   Milestone:
Component:  varnishd     |     Version:  3.0.2
 Severity:  major        |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by martin):

 This is because in stock Varnish persistence, the persisted ban space is a
 fixed size that cannot be reclaimed. When the space is exhausted, the silo
 becomes unusable. So in stock Varnish persistence, it is not advisable to
 rely on bans for cache invalidation.

 This is planned fixed with Varnish release 4, that will contain fixes in
 this area. Leaving ticket open until the necessary bits have been fully
 merged.

 (The -plus branch contains a preview of fixes that correct this behavior.
 While this is open source, there is no community driven support available
 (https://github.com/mbgrydeland/varnish-cache/tree/3.0.3-plus)).

 Regards,
 Martin Blix Grydeland

-- 
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1083#comment:6>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator