[Squid Rewritter] Issue with the concurrency option

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[Squid Rewritter] Issue with the concurrency option

ygirardin
Hi,


I'm working on updating my squid which was running under the 3.3.8
version to the new 4.2 release.


I'm using rewriter with concurency like this

url_rewrite_children 100 startup=10 idle=2 concurrency=5 queue-size=10
on-persistent-overload=ERR


So according to the documation I should be receive data with channel-id
going through 0 to concurrency. It was the case in 3.3.8 but with 4.2 I
never received anything in channel 0 and I sometimes receive data on my
helper stdin with channel id bigger than 5

This is what I receive


6 http://10.1.39.1:9123/redirect/?SessionID=64012081 10.1.0.39/10.1.0.39
- GET myip=10.1.39.1 myport=3128

Is that normal ?


Thanks



_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|

Re: [Squid Rewritter] Issue with the concurrency option

Amos Jeffries
Administrator
On 21/08/18 10:16 PM, ygirardin wrote:

> Hi,
>
> I'm working on updating my squid which was running under the 3.3.8
> version to the new 4.2 release.
>
>
> I'm using rewriter with concurency like this
>
> url_rewrite_children 100 startup=10 idle=2 concurrency=5 queue-size=10
> on-persistent-overload=ERR
>
>
> So according to the documation I should be receive data with channel-id
> going through 0 to concurrency.

Which documentation is giving you that?

'concurrency' is the limit on number of requests Squid has in flight to
the helper.

The channel-ID is an opaque value that should be unique for each line
sent to the helper.


> It was the case in 3.3.8 but with 4.2 I
> never received anything in channel 0 and I sometimes receive data on my
> helper stdin with channel id bigger than 5
>
> This is what I receive
>
>
> 6 http://10.1.39.1:9123/redirect/?SessionID=64012081 10.1.0.39/10.1.0.39
> - GET myip=10.1.39.1 myport=3128
>
> Is that normal ?
>

Yes.

The on-persistent-overload=ERR option allows for more than the N of
concurrency=N requests to be not-yet-responded in the helper at once.
Squid does not tell the helper which lookups it has given up on and
produced the ERR for - it just sends another lookup.

Amos
_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|

Re: [Squid Rewritter] Issue with the concurrency option

Alex Rousskov
On 08/21/2018 08:53 AM, Amos Jeffries wrote:
> On 21/08/18 10:16 PM, ygirardin wrote:
>> I'm working on updating my squid which was running under the 3.3.8
>> version to the new 4.2 release.

>> according to the documation I should be receive data with channel-id
>> going through 0 to concurrency.


> Which documentation is giving you that?

FWIW, 0..concurrency numbering of the first helper request field is a
very natural (but no longer correct) interpretation of that field name
-- "channel ID". IMHO, Squid documentation should be rewritten to use
"transaction ID" instead. Pull requests and wiki updates are welcomed.

What used to be a small channel ID from a 0..concurrency interval, is
now an ever-increasing/unique (within a helper instance scope) 64-bit
transaction ID. There is (a somewhat veiled IMHO) explanation about that
in Squid v4 release notes:

http://www.squid-cache.org/Versions/v4/RELEASENOTES.html#ss2.2


HTH,

Alex.
_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|

Re: [Squid Rewritter] Issue with the concurrency option

Amos Jeffries
Administrator
On 22/08/18 9:05 AM, Alex Rousskov wrote:

> On 08/21/2018 08:53 AM, Amos Jeffries wrote:
>> On 21/08/18 10:16 PM, ygirardin wrote:
>>> I'm working on updating my squid which was running under the 3.3.8
>>> version to the new 4.2 release.
>
>>> according to the documation I should be receive data with channel-id
>>> going through 0 to concurrency.
>
>
>> Which documentation is giving you that?
>
> FWIW, 0..concurrency numbering of the first helper request field is a
> very natural (but no longer correct) interpretation of that field name
> -- "channel ID". IMHO, Squid documentation should be rewritten to use
> "transaction ID" instead. Pull requests and wiki updates are welcomed.

That won't help if it is external documentation. Which is why I asked.
All but one place we have simply calls it "channel-ID", that one says
"channel number" but no text about how it behaves.

Amos
_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|

Re: [Squid Rewritter] Issue with the concurrency option

ygirardin
The documentation is directly extract from the squid website :

http://www.squid-cache.org/Doc/config/url_rewrite_program/

Thanks for the feedback

-----Message d'origine-----
De : squid-users [mailto:[hidden email]] De la part de Amos Jeffries
Envoyé : mercredi 22 août 2018 04:57
À : [hidden email]
Objet : Re: [squid-users] [Squid Rewritter] Issue with the concurrency option

On 22/08/18 9:05 AM, Alex Rousskov wrote:

> On 08/21/2018 08:53 AM, Amos Jeffries wrote:
>> On 21/08/18 10:16 PM, ygirardin wrote:
>>> I'm working on updating my squid which was running under the 3.3.8
>>> version to the new 4.2 release.
>
>>> according to the documation I should be receive data with channel-id
>>> going through 0 to concurrency.
>
>
>> Which documentation is giving you that?
>
> FWIW, 0..concurrency numbering of the first helper request field is a
> very natural (but no longer correct) interpretation of that field name
> -- "channel ID". IMHO, Squid documentation should be rewritten to use
> "transaction ID" instead. Pull requests and wiki updates are welcomed.

That won't help if it is external documentation. Which is why I asked.
All but one place we have simply calls it "channel-ID", that one says
"channel number" but no text about how it behaves.

Amos
_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users