[squid-users] sourcehash load balance

[Amos Jeffries]

On 22/10/2016 12:21 a.m., André Janna wrote:
> I set up a Squid proxy that forwards all requests to 2 parent caches.
> I'm using Squid version 3.5.19.
> My goal is that multiple connection from a client to a server should be
> forwarded to the same parent, so that the server see all requests coming
> from the same IP address.
> 
> I'm using the following configuration:
> cache_peer squid1 parent 3128 0 no-query sourcehash
> cache_peer squid2 parent 3128 0 no-query sourcehash
> never_direct allow all
> 
> Looking at access.log some requests are tagged as CLOSEST_PARENT instead
> of SOURCEHASH_PARENT, so it seams that Squid is not always using source
> hash rule to forward requests to parent caches.
> For instance:
> 1477046954.047   3882 10.11.2.4 TCP_TUNNEL/200 21935 CONNECT
> sso.cisco.com:443 - SOURCEHASH_PARENT/10.0.33.12 -
> 1477046968.056     21 10.11.2.4 TCP_MISS/200 1012 POST
> http://ocsp.digicert.com/ - CLOSEST_PARENT/10.0.33.13
> application/ocsp-response
> 1477047782.038     22 10.11.2.4 TCP_MISS/204 307 GET
> http://clients1.google.com/generate_204 - SOURCEHASH_PARENT/10.0.33.12 -
> 1477047782.045    181 10.11.2.4 TCP_MISS/200 745 GET
> http://tags.bluekai.com/site/2964? - CLOSEST_PARENT/10.0.33.13 image/gif
> 
> So requests from the same client are not sent to the same parent cache.
> How can I force Squid to always use source hash parent selection method?

Check you setting for nonhierarchical_direct. It should be 'off'. The
default is 'on'.

Amos