In message <[email protected]>, Micha el Fischer writes:
>> In message <[email protected]>, >> David >> Birdsong writes: >> >> >Right, but those 2 remaining are at least still being asked for the >> >same url's they were prior to the 1 dying. >> >> Correct, the hashing is "canonical" in the sense that if the >> configured backend is up, all traffic for "its" objects will be >> sent to it. > >Are you saying that the default hash is not a mod-n-type algorithm? Well, it is mod-n, with the footnote that n has nothing to do with the number of backends, because these have a configurable weight. >If not, what happens when the failed backend is restored to service? It's probably simplest to paraphrase the code: Calculate hash over full complement of backends. Is the selected backend sick Calculate hash over subset of healthy backends -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [email protected] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ varnish-misc mailing list [email protected] http://projects.linpro.no/mailman/listinfo/varnish-misc
