public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pasky at suse dot cz" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nscd/6812] nscd doesn't handle temporary resolver errors properly Date: Thu, 26 Aug 2010 23:00:00 -0000 [thread overview] Message-ID: <20100826230047.25615.qmail@sourceware.org> (raw) In-Reply-To: <20080801100019.6812.jsembera@suse.cz> ------- Additional Comments From pasky at suse dot cz 2010-08-26 23:00 ------- I do not think it is appropriate on two counts. First, caching temporary results would not be specific to this cache and would be a completely orthogonal nscd-wide change, so I do not think the patch should be judged based on this at all. Second, the idea of caching intermittent failures itself seems strange to me. The situation itself should happen only in relatively exceptional cases, usually due to some network outage - in that case, it is not clear the benefit of giving quicker feedback to the application outweights the disadvantage of prolonging service outages or even massively amplifying mere singular errors. After all, the return code specifically says "try again", and it is quite plausible the application will go to some limited loop where it tries to re-resolve after very short interval. In short, I am worried about the amplification of singular failures, and noone showed up so far who would actually want to cache intermittent failures to cater for some plausible scenario. -- http://sourceware.org/bugzilla/show_bug.cgi?id=6812 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-08-26 23:00 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-08-01 10:01 [Bug nscd/6812] New: " jsembera at suse dot cz 2008-08-01 10:03 ` [Bug nscd/6812] " jsembera at suse dot cz 2008-08-01 10:17 ` jsembera at suse dot cz 2008-08-01 12:03 ` pasky at suse dot cz 2010-04-15 12:34 ` jsembera at suse dot cz 2010-06-01 2:18 ` pasky at suse dot cz 2010-08-23 20:24 ` drepper at redhat dot com 2010-08-26 23:00 ` pasky at suse dot cz [this message] 2010-09-13 18:46 ` drepper at redhat dot com 2010-09-21 14:01 ` pasky at suse dot cz [not found] <bug-6812-131@http.sourceware.org/bugzilla/> 2011-01-15 16:11 ` drepper.fsp at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20100826230047.25615.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).