Thanks for the rapid response, Henrik.
Henrik Nordstrom wrote:
On Thu, 7 Apr 2005, Joe Cooper wrote:
The whole configuration is working, except for load balancing. Without "carp" I always get FIRST_UP_PARENT/192.168.1.47. With "carp" I always get CARP/192.168.1.48, no matter what IP I'm coming from (and I tried a half dozen client IPs to be sure I wasn't just coincidentally always hashing to the same destination).
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?
You can get quite detailed tracing of the CARP hashing by enabling debug section 39,9, combined with the cachemgr carp section.
Excellent. Thanks for the tip.
