[chord] Trace to the lookup process

Hai Dao Le daolehai at nm.gist.ac.kr
Tue Jan 9 21:51:28 EST 2007


Thanks so much. That helps me a lot.

Best regards,

Hai

-----Original Message-----
From: Emil Sit [mailto:sit at MIT.EDU] 
Sent: Wednesday, January 10, 2007 12:38 AM
To: Hai Dao Le
Cc: chord at amsterdam.lcs.mit.edu
Subject: Re: [chord] Trace to the lookup process

On Sun, 07 January 2007 at 21:12 (+0900), Hai Dao Le wrote:
> One more thing, when seeing the log files at those nodes, only two of
> them have the output regarding to the lookup key (7777...).

Ah... it appears that over time, some slightly incompatible changes
were made to the semantics of the CHORDPROC_FINDROUTE RPC and the
findroute utility.

Can you try the following change?  In tools/findroute.C, 

@@ -53,6 +51,7 @@ findroute(chordID key)
 {
   ptr<chord_findarg> fa = New refcounted<chord_findarg> ();
   fa->x = key;
+  fa->return_succs = false;
   chord_nodelistres *route = New chord_nodelistres ();
   starttime = getusec ();
   doRPC (dst, chord_program_1,

What is happening is that the output you are seeing includes
some nodes from the successor list, in addition to the path.
This change should prevent the successor nodes from being
returned and bring the output in-line with what you are seeing
in your logs.

-- 
Emil Sit / MIT CSAIL PDOS / http://pdos.csail.mit.edu/chord/  




More information about the chord mailing list