toad wrote: > What's the difference between search failure, RNF and DNF? Search > failure is a timeout?
"failed (search)" means the search timed out at the originating node - a peer accepted the search but then didn't return a result. "failed (rnf)" means the search ran out of nodes before running of hops. However, this could be caused by timeouts, because if we time out waiting for a peer to accept the search we move on to another peer. "failed (dnf)" means the search ran out of hops before running out of nodes. This only applies to requests, not inserts, and doesn't indicate a timeout. > If so, this is with throttling? There shouldn't be > _that_ many timeouts... Agreed, timeouts should be rare with any kind of flow control. I believe the results Jano posted were without flow control. It seems that RNFs can indicate overload, not just bad connectivity, but when we get an RNF we *increase* the throttle. I might not have understood this correctly - after rereading your message (copied below) it looks like maybe this should only apply to inserts, not requests? > On Sat, Nov 18, 2006 at 12:10:39PM +0000, Michael Rogers wrote: >> > If an insert generates a RouteNotFound but we successfully sent the data >> > to at least one node, should we count it as a success or a failure from >> > the point of view of throttling? > > Success. From the point of view of throttling, it's only a failure if we > get a RejectedOverload or a timeout. Cheers, Michael
