[squid-users] squid cache peer not rotating over round robin !

[Amos Jeffries]

On 05/09/17 07:17, --Ahmad-- wrote:
> hello folks
> 
> I’m trying to rotate squid request over several peers
> my config are below but they are only stuck with 1 peer .
> 
> acl custNet dstdomain  .trustly.com  .ing.nl  .adyen.com .rabobank.nl .abn.nl .iplocation.net .abnamro.com .abnamro.nl .abnamro.nl
> cache_peer 66.78.18.1 parent 41311 0 no-query round-robin no-digest no-tproxy proxy-only
> cache_peer 66.78.18.2 parent 41311 0 no-query round-robin no-digest no-tproxy proxy-only
> cache_peer 66.78.18.3 parent 41311 0 0 no-query round-robin no-digest no-tproxy proxy-only
> cache_peer 66.78.18.4 parent 41311 0 0 no-query round-robin no-digest no-tproxy proxy-only
> cache_peer 66.78.18.5 parent 41311 0 no-query round-robin no-digest no-tproxy proxy-only
> cache_peer 66.78.18.6 parent 41311 0 no-query round-robin no-digest no-tproxy proxy-only
> cache_peer 66.78.18.7 parent 41311 0 no-query round-robin no-digest no-tproxy proxy-only
> cache_peer 66.78.18.8 parent 41311 0 no-query round-robin no-digest no-tproxy proxy-only
> cache_peer 66.78.18.9 parent 41311 0 no-query round-robin no-digest no-tproxy proxy-only
> #####################
> never_direct allow custNet
> http_access allow custNet
> 
> 
> any idea what wrong with round robin above ?
> 

The lines for peer *.3 and *.4 contain an extra '0' in the options area 
after ICP-port which may be preventing Squid from loading this config.

Other than that nothing is visible from the details you mention.


Some random possibilities:

* Check that all peers are detected as ALIVE by Squid. Peers that are 
marked as DEAD (10 consecutive failures occured) are skipped in the load 
balancing algorithms. That 'no-query' disables the UDP checks used to 
detect peers going from DEAD to LIVE status, so error recovery will be 
quite slow.


* Check that the "requests" you are referring to are not all inside a 
single CONNECT tunnel. Tunnels count as a single request in plain-text 
HTTP no matter how much 'crypted traffic they contain.


I assume this is the same 3.5.22 you mentioned using in threads from a 
few days ago.

Amos