[Bug nscd/6812] nscd doesn't handle temporary resolver errors properly

["pasky at suse dot cz" <sourceware-bugzilla at sourceware dot org>]

------- 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.