On 16/09/2016 8:19 p.m., yanghe wrote:
> On 09/14/2016 09:51 PM, wrote: "Alex Rousskov"
>> Unfortunately, Squid does not support true load
>> However, there is a workaround: Use
>
> Thanks for your adivice.
> IF I do not use adaptation_service_set or adaptation_service_chain to list N c-icap services.the traffic will only go to the first.
> Get your advice.I tried configure the "random" ACLs,But,It is not successful
> Here is my squid.conf
> balance_on_multiple_ip on
> acl halfpercent random 0.5
> tcp_outgoing_address 192.168.1.4 halfpercent
> tcp_outgoing_address 192.168.1.2
>
> icap_service service_req reqmod_precache bypass=0 icap://192.168.1.4:1344/echo
> adaptation_access service_req allow all
>
> icap_service service_req_two reqmod_precache bypass=0 icap://192.168.1.2:1344/echo
> adaptation_access service_req_two allow all
This is *not* what Alex advised.
tcp_outgoing_address is the IP Squid will use to contact upstream web
servers. Dont do that.
What Alex suggested was to use the random ACL in your
*adaptation_access* rules to select ICAP service for use.
Getting the right random value to check against is tricky though. I'm
not sure what the calculation should be here. Maybe this:
acl half random 0.5
icap_service service_req reqmod_precache \
bypass=0 icap://192.168.1.4:1344/echo
adaptation_access service_req allow half
icap_service service_req_two reqmod_precache \
bypass=0 icap://192.168.1.2:1344/echo
adaptation_access service_req_two allow all
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
