On Wed, 4 May 2011 14:03:12 -0300, igor rocha wrote:
hello,
have something in question that i does not make it clear?
No, the problem seems clear now. Reason for it is a mystery.
I didn't answer to see if anyone else knew of it and would post, but
apparently not. Time for some deep digging on your part.
"debug_options 44,6" will log the peer selection logic debug into
cache.log for use in figuring this out.
Amos
Thanks
2011/5/2 igor rocha <igorlogos@xxxxxxxxx>
hello,
no, this is not the problem, it was a typo, I checked in my file and
it are with -, ie to round-robin .
2011/5/2 Amos Jeffries:
> On Mon, 2 May 2011 18:07:53 -0300, igor rocha wrote:
>>
>> See, I'm configuring my squid.conf intending it to run in mesh:
>>
>> cache_peer 192.168.15.200 parent 3128 0 no-query round robin
>> cache_peer 192.168.15.201 parent 3128 0 no-query round robin
>> cache_peer 192.168.15.202 parent 3128 0 no-query round robin
>> cache_peer 192.168.15.203 parent 3128 0 no-query round robin
>>
>> My scenario is that there are four nodes, a front-end and the
other
>> nodes. As it is configured, when sent to the node IP , he
accumulates
>> more bytes than the other three nodes. I wonder whether we can
make an
>> ideal balancing ? If yes, how to do it?
>
> You are missing a "-" in the option name "round-robin". If Squid
is
ignoring
> them that would drop you back to the default first-available
logics which
> acts like you describe.
hello,
no, this is not the problem, i erred in the hour of the copy, I
checked in my file and it are with -, ie to round-robin .
>
> Amos
>
>
