Poul-Henning Kamp wrote:
The critical question is how we define backend is down and how
fast and efficient we can detect it.
Ideas for how to express it in VCL are very welcome.
Maybe naive:
# First, we setup decide how to sniff that a backend is down
#
# options_ping: Send a HTTP OPTIONS
Christoph [EMAIL PROTECTED] writes:
So what is dirty caching and why use it? Think of a very unreliable
backend. If varnish can't reach it's backend, it will simply return
the last content it has (even if the content is stale). That way i can
cover hickups.
It's on our list for 2.0, and will
- Dag-Erling Smørgrav [EMAIL PROTECTED] wrote:
Christoph [EMAIL PROTECTED] writes:
So what is dirty caching and why use it? Think of a very unreliable
backend. If varnish can't reach it's backend, it will simply return
the last content it has (even if the content is stale). That way i
In message [EMAIL PROTECTED], Christoph writes:
i'd like to implement dirty-caching using varnish.
I'm busy twisting the variable visibility in VCL into proper shape
right now, and that will move us a bit closer to what your want
to do.
The critical question is how we define backend is down and
Poul-Henning Kamp wrote:
The critical question is how we define backend is down and how
fast and efficient we can detect it.
Right. I tend to like the Perlbal approach: Issue a http OPTIONS and
check if we get anything back from the backend. It is quite lightweight.
/Anton
hi,
i'd like to implement dirty-caching using varnish.
So what is dirty caching and why use it? Think of a very unreliable
backend. If varnish can't reach it's backend, it will simply return the
last content it has (even if the content is stale). That way i can cover
hickups.
Is this possible?
