Hi Jonathan,
What you could do is something like;
backend squid_1 {
...
}
backend backend_1 {
...
}
director prefer_squid random {
.retries = 1;
{
.backend = squid_1
.weight = 250;
}
{
.backend = backend_1;
.weight = 1;
}
}
This will make sure varnish will retrieve data from the squids mostly
and gives you the chance to do the migration in your own time.
Regards,
Martin
On 03/25/2011 11:55 AM, Jonathan Matthews wrote:
On 21 March 2011 15:08, Jonathan Matthews<[email protected]> wrote:
Hi all -
I've got some long-running squid instances, mainly used for caching
medium-sized binaries, which I'd like to replace with some varnish
instances. The binaries are quite heavy to regenerate on the distant
origin servers and there's a large number of them. Hence, I'd like to
use the squid cache as a target to warm a (new, nearby) varnish
instance instead of just pointing the varnish instance at the remote
origin servers.
The squid instances are running in proxy mode, and require (I
*believe*) an HTTP CONNECT. I've looked around for people trying the
same thing, but haven't come across any success stories. I'm
perfectly prepared to be told that I simply have to reconfigure the
squid instances in mixed proxy/origin-server mode, and that there's no
way around it, but I thought I'd ask the list for guidance first ...
Any thoughts?
Anyone? All opinions welcome ... :-)
_______________________________________________
varnish-misc mailing list
[email protected]
http://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
