[squid-users] cache_peer: userhash imply also sourcehash?

From: Tom Tux <tomtux80_at_gmail.com>
Date: Tue, 10 May 2011 10:46:52 +0200

Hi

Why does the option "userhash" on the cache_peer-directive also
implies the "sourcehash"-option?

I have the following cache_peer-directives:
cache_peer xx.xx.xx.x1 parent 1234 0 no-query
no-digest connect-fail-limit=5 userhash
cache_peer xx.xx.xx.x2 parent 1234 0 no-query
no-digest connect-fail-limit=5

The output from squidclient mgr:server_list gives me the following back:

HTTP/1.0 200 OK
Server: squid/3.1.6
Mime-Version: 1.0
...
...
Parent : xx.xx.xx.x1
Host : xx.xx.xx.x1/1234/0
Flags : no-query no-digest userhash sourcehash
connect-fail-limit=5 connection-auth=auto
Address[0] : xx.xx.xx.x1
Status : Up
FETCHES : 0
OPEN CONNS : 0
AVG RTT : 0 msec
IGNORED : 0 0%
keep-alive ratio: 0%

Parent : xx.xx.xx.x2
Host : xx.xx.xx.x2/1234/0
Flags : no-query no-digest connect-fail-limit=5 connection-auth=auto
Address[0] : xx.xx.xx.x2
Status : Up
FETCHES : 0
OPEN CONNS : 0
AVG RTT : 0 msec
IGNORED : 0 0%
keep-alive ratio: 0%

Why does the parent xx.xx.xx.x1 has the flag "sourcehash" included?
Will the peer-selection-method in this case really includes both
(source- and userhash)?
When I just add "sourcehash", then I can't see sourcehash nor
userhash. The same behavior also with squid 3.1.9.

Thanks a lot for hints.
Tom
Received on Tue May 10 2011 - 08:46:58 MDT

This archive was generated by hypermail 2.2.0 : Tue May 10 2011 - 12:00:02 MDT