HyperTree for self-stabilizing peer-to-peer systems

Shlomi Dolev, Ronen I. Kat

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

10 Scopus citations

Abstract

Peer-to-peer systems are prone to faults, thus it is vitally important to design peer-to-peer systems to automatically regain consistency, namely to be self-stabilizing. Toward this goal, we present a deterministic structure that defines for every n the entire (IP) pointers structure among the n machines. Namely, the next hop for the insert, delete and search procedures of the peer-to-peer system. Thus, the consistency of the system is easily defined, monitored, verified and repaired. We present the HyperTree (distributed) structure which support the peer-to-peer procedures while ensuring that the out-degree and in-degree (the number of outgoing/incoming pointers) are b logb N where N in the maximal number of machines and b is an integer parameter greater than 1. In addition the HyperTree ensures that the maximal number of hops involved in each procedure is bounded by logb N. A self-stabilizing peer-to-peer system based on the HyperTree is presented.

Original languageEnglish
Title of host publicationProceedings - Third IEEE International Symposium on Network Computing and Applications, NCA 2004
Pages25-32
Number of pages8
DOIs
StatePublished - 1 Dec 2004
EventProceedings - Third IEEE International Symposium on Network Computing and Applications, NCA 2004 - Cambridge, MA, United States
Duration: 30 Aug 20041 Sep 2004

Publication series

NameProceedings - Third IEEE International Symposium on Network Computing and Applications, NCA 2004

Conference

ConferenceProceedings - Third IEEE International Symposium on Network Computing and Applications, NCA 2004
Country/TerritoryUnited States
CityCambridge, MA
Period30/08/041/09/04

ASJC Scopus subject areas

  • General Engineering

Fingerprint

Dive into the research topics of 'HyperTree for self-stabilizing peer-to-peer systems'. Together they form a unique fingerprint.

Cite this