improve termination of lookup #53

New issue

Open

opened 2020-06-25 17:42:38 +02:00 by schmittlauch · 0 comments

schmittlauch commented

2020-06-25 17:42:38 +02:00

Owner

similar to #52

From the Epichord tech report paper:

In general, we can terminate a get() lookup operation and return
when the target id falls between a responding node and its successor
or predecessor or whenever a node returns the requested object. How-
ever, if the node failure rate is high, we may choose to terminate a
put() lookup operation only after both the best predecessor and best
successor respond and we check that they are consistent (i.e., that think
that they are adjacent to each other in the address space).

similar to #52 From the [Epichord tech report](http://publications.csail.mit.edu/lcs/pubs/pdf/MIT-LCS-TR-963.pdf) paper: > In general, we can terminate a get() lookup operation and return when the target id falls between a responding node and its successor or predecessor or whenever a node returns the requested object. How- ever, if the node failure rate is high, we may choose to terminate a put() lookup operation only after both the best predecessor and best successor respond and we check that they are consistent (i.e., that think that they are adjacent to each other in the address space).