FYI, continuing in Varnish 2.1 persist does not offer persistence across a parent restart (via process restart, process crash, or host crash).
I do understand that there is some benefit to persistent storage in the case of the child crashing. But in any situation where I could not survive the child crashing (origin spike), I couldn't survive the parent bouncing, either. To me the difference between file and persist is academic; am I missing something either in the implementation or the intent of this feature? Thanks, -- kb On Jan 27, 2010, at 12:08 PM, Ken Brownfield wrote: > Right, -spersistent. Child restarts are persistent, parent process > stop/start isn't. > > Maybe there's a graceful, undocumented method of stopping the parent that I'm > not aware of? > -- > kb > > On Jan 27, 2010, at 1:26 AM, Tollef Fog Heen wrote: > >> ]] Ken Brownfield >> >> | I'd love to test persistent under production load, but right now it's >> | not persistent. :-( (Storage doesn't persist through a parent restart) >> >> That sounds like a real bug. Just to be sure, you're testing with >> -spersistent, not -smalloc or -sfile? >> >> -- >> Tollef Fog Heen >> Redpill Linpro -- Changing the game! >> t: +47 21 54 41 73 >> _______________________________________________ >> varnish-misc mailing list >> [email protected] >> http://projects.linpro.no/mailman/listinfo/varnish-misc > _______________________________________________ varnish-misc mailing list [email protected] http://lists.varnish-cache.org/mailman/listinfo/varnish-misc _______________________________________________ varnish-misc mailing list [email protected] http://lists.varnish-cache.org/mailman/listinfo/varnish-misc
