Hello, Last night after your reply, I put a ban_cutoff value of 18500 according to the definition (50ms of latency, 370K/s ban.lurker.tested) (I've restarted varnish, "varnishadm param.show ban_cutoff" shows the right value)
This morning, nothing has changed : ban lists is increasing (well over 18500). https://pasteboard.co/GI1K682.png Regards Olivier 2017-08-30 8:47 GMT+02:00 Olivier Hanesse <[email protected]>: > Hello Dridi, > > Thanks for your reply. > I must admit I didn't understand perfectly the description of this option. > > What will happen when the ban list hits the size of bans defined in > ban_cutoff value ? > > Will the ban list be truncated and all the previous (oldest ?) bans will > be simply deleted without purging the cache ? > Or will varnish suspend other regular requests (increasing the lurker > priority thread , something like that ?) until the ban list size is under > this value ? > > Regards > > Olivier > > > 2017-08-29 19:04 GMT+02:00 Dridi Boukelmoune <[email protected]>: > >> > I've already tried to change (increase/decrease) both >> "ban_lurker_batch" and >> > "ban_lurker_sleep" parameters. Same things. >> > >> > I don't know how I can get more lurker logs to debug this. >> > Is there a way to make it more aggressive ? >> > >> > Any ideas ? >> >> Did you look at the ban_cutoff parameter? >> >> I think it landed in the 5.1 series. >> >> Dridi >> > >
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
