Hello Alex,
Thanks for your answer.
>> We are using two squid proxies (Squid 3.3)
>Squid v3 is not officially supported. My answers below may apply to
>Squid v3, but they are based on Squid v5+.
>> In order to address some issues with Java clients, we tried to lower
>> the worker directive fr
Thank you, Alex and Eli,
Just wanted to update that I was able to solve the problem in case someone runs
into it in the future,
based on Eliezers suggestion, I disabled logrotate (although it can be tweaked
to work), and just wrote
a custom cron job to run daily and rotate the logs for each squi
Hello,
I have just recently started exploring ingesting logs from Squid via Logstash
(TCP log ingestion)
I now have to make the decision of how to deploy Logstash, it seems to me that
I have two options:
1. Deploy a Logstash instance for every region where I have a Squid instance
running, res
On 9/9/22 04:20, Xavier Lecluse wrote:
In order to address some issues with Java clients, we tried to lower
the worker directive from 8 to 1, because of the relative low number
of simultaneous connections on our SSquid servers (about 100rq/s)
After reducing the worker value to 1, and restarting t
On 9/9/22 08:49, roee klinger wrote:
Hello,
I have just recently started exploring ingesting logs from Squid via
Logstash (TCP log ingestion)
I now have to make the decision of how to deploy Logstash, it seems to
me that I have two options:
1. Deploy a Logstash instance for every region w
On 9/9/22 18:29, Praveen Ponakanti wrote:
On Thu, Sep 8, 2022 at 8:31 PM Alex Rousskov wrote:
On 9/8/22 19:41, Praveen Ponakanti wrote:
> * We have a large number of workers (30) to help with handling a
> high RPS. However, TCP session reuse does not seem to be optimal
