Re: originserver plus carp configuration?

On Thu, 7 Apr 2005, Joe Cooper wrote:

>> CARP balances based on a hash of the destination URL, not client.
>
> Hmmm...that raises a different question: How does one address the issue of
> maintaining client stickiness?

It doesn't. CARP is designed for routing requests to a cloud/array of
parent proxy cache servers with minimal duplication of cache content.

doc/rfc/draft-vinod-carp-v1-03.txt

it's positive properties are

   - Deterministic static forwarding path. The same URL always gets the
same forwarding part while the configuration is the same.

   - Minimal cache distruption on changes. If a member server is
added/removed from the array only a portion of the cache in proportion to
the size/power of the added/removed server is affected by the change.

   - No peering traffic. Thanks to the deterministic static forwarding
path.

it's negative properties are

   - Static forwarding path. Can not easily adjust to dynamic changes in
weights / server capacity.

   - Forwarding is based on a hash of the complete URL. No client
or even destination persisance.

Regards
Henrik
Received on Thu Apr 07 2005 - 18:23:39 MDT