]] pablort
| The numbers do reflect the TxStatus'es that I see in interactive varnishtop,
| but when I try to run it with -1, it doesn't show which entry corresponds to
| which status. LOL.
You're running an old version, this was fixed in 2.0.5 so upgrading
should fix that.
--
Tollef Fog Heen
]] Abhishek Singh
| I am using varnish for static files caching and multiple domains are getting
| served from varnish cluster and i want to purge static files for specific
| domain so how can i do that.
|
| I tired following but it is not working.
|
| 1)
| purge req.http.host ~ xyz.com
| 101
Poul-Henning Kamp p...@phk.freebsd.dk wrote :
Let's get back to consistent hashing and it's use...
Correct me if I am wrong, but doesn't this mean that adding a new
varnish instance implies a full rehash ?
Yes, that is pretty much guaranteed to be the cost with any
stateless hashing.
]] Ken Brownfield
| Right, -spersistent. Child restarts are persistent, parent process
stop/start isn't.
It should be. You'll lose the last storage silo (since that's not
closed yet), but older objects should be available.
Can you see if you can reproduce and post a varnishlog -1 when the
1) 8 (All servers are serving from mem, big machines. 6 as frontend in
cluster and load balanced, 1 as between frontend varnish and backend
application server and 1 as backup)
2) ~250MB/s (through varnish). 2.5m visitors a day, 27m pageviews a day
(for the whole website, some content doesn't go
On Jan 29, 2010, at 3:54 AM, Tollef Fog Heen wrote:
It should be. You'll lose the last storage silo (since that's not
closed yet), but older objects should be available.
This might be the source of the confusion. How often are silos closed? My
testing was simply hit the cache for a single
