Canon in G Major: Designing DHTs with Hierarchical Structure Prasanna Ganesan(Stanford University) Krishna Gummadi(University of Washington) Hector Garcia-Molina(Stanford Universiy)
Motivating Scenario P-2-P Application –File sharing –Multi-media sharing –Collaborative computation –General purpose lookup directories
Motivating Scenario Where is the paper “Canon in G Major”?
Hierarchy Design Single Point Over Head Isolating faults Adapting growth
Flat Design(DHT) No single point of failure
Flat & Hierarchical Design Flat Design –No single point of failure –P2P(DHT) Hierarchical Design –Isolating faults –Adapting growth –DNS
Canonical System
Crescendo Chord Merged Chord
Chord Circular N-bit ID space Node x links to succ(x+2^i)
Crescendo Merge –Merging multiple rings –Multi-level hierarchies Incremental –New node joins bottom up Links per node –Log(n)
Merging
Merging Rule –Closer than any other black node –Y=succ(x+2^i)
Routing Crescendo (intra-domain) Greedy Clockwise routing Path Locality -Fault isolation -Security -Efficiency 0 -> 12
Routing Crescendo (inter-domain) Path convergence :closest node to destination in the domain :same destination node same last node in the domain 0 -> 13 -Distributed Caching -Bandwidth savings 5 -> 13
Other DHTs Chord => Crescendo CAN => Can-Can Symphony => Cacophony Kademlia => Kandy
Evaluation Links/node Hops/query latency
Number of Links vs. Number of Levels
Levels vs. Routing Hops
Path Locality
Critique Strong point –Novel Idea –Good development of idea Weak point –Poor motivating scenario
New Idea Do you have any New Idea?