[squid-users] Survey on assertions: When the impossible happens

Yuri Voinov yvoinov at gmail.com
Tue Mar 1 18:23:51 UTC 2016


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
 


01.03.16 23:37, Alex Rousskov пишет:
> On 03/01/2016 03:55 AM, Eray Aslan wrote:
>> On Mon, Feb 29, 2016 at 09:43:09AM -0700, Alex Rousskov wrote:
>>> Q2: Your Squid is asserting every 5 minutes. There is no [working] Squid
>>> version you can switch to. Your network topology does not allow you to
>>> bypass Squid. Until the bug is fixed, would you prefer to see fewer
>>> assertions in exchange for more memory leaks and an increased
>>> probability of malformed/corrupted/misleading HTTP messages?
>
>> False dichotomy.
>
> Unfortunately, it is often a real one. In the real world, Squid is often
> a single point of failure without good bypass options.
BTW,

there is a good one solution. Transparent proxy with WCCPv2. WCCPv2 has
good HA and bypass option.
>
>
>
>> Worst case:  Live through the outage, learn from it
>
> Learning from failures is hardly the worst case. The worst cases in the
> real world include innocent admins losing their jobs, kids exposed to
> content they cannot unsee, etc., etc. It should not be that way, but it
> sometimes is.
>
>
>> and hopefully design your systems accordingly in the future.
>
>
> These questions are exactly about "designing your systems" better! Squid
> is a "system" itself, and if you think that there is always a way to
> bypass Squid, then it should be easy for you to accept the same [false]
> premise that there is always a way to bypass an assertion inside Squid.
> Designing Squid to bypass internal failures is what options #2 and #3
> are about. Same premise, same architectural principles, different zoom
> level.
Absolutely right.
>
>
>
> Cheers,
>
> Alex.
>
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
 
iQEcBAEBCAAGBQJW1d43AAoJENNXIZxhPexGN90H/Ar3Zeh95aRRbX1mXbQTTGhw
MViOJAjMp8Mhnv3Ivna9h/bh4DHJ86Uej8VhYbaCrIVqOB3Th5/gUMbk2CytRiCT
LlqXsWPH+qBEESWK4HrPU7SaXB4sskWcqMQvGYf57NbPMNQEUA1h20aJm3Ua/KWY
2IF0e0GvWIC9oG2iNTk6scjjakqPiJr7ccrTomIaQmAZZSYGVNQ5F+V8FtIwx0s6
7gzuBIXd+R/SJtxyBGoppr/YVT9YUhHQ3AmB3IClJQJi6OcBBZSs4MpkT4nofaMz
65VQz/AgLk5EPrrvg8o2fq4RTJEmbbyvHVqp+Cle79cI22keLWgy5HH3a5/Eh/Q=
=eRWw
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x613DEC46.asc
Type: application/pgp-keys
Size: 2437 bytes
Desc: not available
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20160302/17d1f152/attachment.key>


More information about the squid-users mailing list