[chord] Trace to the lookup process

[Hai Dao Le]

Thanks for your quick reply,

 

I run several vnodes in my machine and look into the output. I think it
should show all of lookup steps in any passed vnode, is that right?
However, I only see one in the requesting node, one in the destination
node (dorecroute), and nothing in any transit node; even though the
final list has 12.

 

Here is an example:

[root at localhost chord-build]# devel/findroute 203.237.53.202 33019
724fef08fffd967b77f2c2658915ff13fc95b47c

Searching for 724fef08fffd967b77f2c2658915ff13fc95b47c from
ede8a5101536e5dff0c2ac75e4caffbbd129ef5f at 203.237.53.202:33019

0: 724fef08fffd967b77f2c2658915ff13fc95b47c 203.237.53.202 33019 10

1: a02974cb1967660ad18180242d968664ed050834 203.237.53.202 33019 8

2: bf34e462507f2945dba1f0b8acf6ee4737c7d574 203.237.53.202 33019 3

3: dd63ef71f9ce4961cca89ceebfe4e559e162b394 203.237.53.202 33019 7

4: e432992ef2be6c1550fbbc8cbb6030b48d266db3 203.237.53.202 33019 11

5: eaf15029ce7203eeb4e6e11078cefaa6858e28fb 203.237.53.202 33019 1

6: ede8a5101536e5dff0c2ac75e4caffbbd129ef5f 203.237.53.202 33019 0

7: 1725a12452d33e871cd8750541b11a35e041637d 203.237.53.202 33019 2

8: 1f6ac4765e1225550d97a7bf442d56a05b2a3d66 203.237.53.202 33019 6

9: 2163891a832b19fc5b4eee1fddc110835651bea4 203.237.53.202 33019 5

10: 330a7b76c8d92a0372cb83b8773565f15bd2898c 203.237.53.202 33019 4

11: 7042b310d4290afcdf14a02b2f780bd9d78f0307 203.237.53.202 33019 9

12: 724fef08fffd967b77f2c2658915ff13fc95b47c 203.237.53.202 33019 10

 key 724f rsz 13 724f a029 bf34 dd63 e432 eaf1 ede8 1725 1f6a 2163 330a
7042 724

 

At the output, only one line from the destination:

7042b310d4290afcdf14a02b2f780bd9d78f0307: dorecroute (2185423133,
724fef08fffd967b77f2c2658915ff13fc95b47c)

 

Best regards,

 

Hai

 

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

 

On Wed, 03 January 2007 at 10:11 (+0900), Hai Dao Le wrote:

> Please let me know how to trace to the lookup process (in recursive

> mode). I guess when a node wants to do a lookup, it first uses

> recroute<T>::dorecroute. If the key is not found, the node then
forwards

> to another by recroute<T>::dorecroute_sendroute. Based on that guess,
I

> put a code to show the trace but I don't have the expected results.
(it

> doesn't show all of the transit nodes as listed in the final result).

 

Can you be a bit more specific about what you want to see?

 

If you just want to print out the path after every lookup,

as seen on the node that started the lookup, you can just modify

vnode_impl::find_successor_cb to print out the search_path.

 

If you want to track the query as it proceeds, each request will

naturally be on a different vnode/lsd/physical-machine and you'll need

to coalesce the logs yourself.  Each recursive routing request has

a unique id that you can use to track a single request.  However,

the requesting machine does not see anything until the lookup

is complete.

 

-- 

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://amsterdam.lcs.mit.edu/pipermail/chord/attachments/20070104/afa7ad1e/attachment.htm