How to set up varnish not be a single point of failure

[Stewart Robinson]

Other people have configured two Varnish servers to be backends for
each other. When you see the other Varnish cache as your remote IP you
then point the request to the real backend. This duplicates your cache
items in each cache.

Be aware of http://www.varnish-cache.org/trac/wiki/VCLExampleHashIgnoreBusy

Stew

On 28 January 2011 10:46, Siju George <sgeorge.ml at gmail.com> wrote:
> Hi,
>
> I understand that varnish does not support cache peering like Squid.
> My planned set up is something like
>
>
>           ---- Webserver1 ---              ------- Cache ---
> ------ API
> LB ----|                          |---- LB----|                    |---- LB
> ----|
>           ---- Webserver2 ---              ------- Cache ---
> ------ API
>
> So if I am using Varnish as Cache what is the best way to configure them so
> that there is redundancy and the setup can continue even if one Cache fails?
>
> Thanks
>
> --Siju
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> http://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>