On 07.01.25 10:49, Tony Albers wrote:
Is it possible in squid to ensure that a badly behaving backend application doesn't eat up all squid resources? E.g.: at work we have an Apache reverse proxy in front of a number of backend hosts. If one of the backend applications misbehaves, this can result in all of apache's worker processes being held up by this application, resulting in apache hanging and all sites going offline. In apache, AFAIK, there is no way to prevent this. But can squid handle this scenario in a way that only the site with the misbehaving application goes offline without pulling the other sites down with it? I understand that the way squid and apache works is different, but that's not really important for me. I just want to use the best tool for the job.
squid handles multiple concurrent connections, so exactly described scenario is unlikely happen with squid. You more likely get maximum munmer of open filedescriptors, but that one can be increased much more than number of apache processes.
-- Matus UHLAR - fantomas, uhlar@xxxxxxxxxxx ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. On the other hand, you have different fingers. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx https://lists.squid-cache.org/listinfo/squid-users
