Peer-to-peer systems were designed from the outset to handle a high rate of churn: node joins, graceful leaves, and failures. Nevertheless, there is a price to church which may manifest itself as dropped messages, increased user-experienced latency, or increased bandwidth use, potentially limiting the scenarios in which a P2P system is deployable. Even in a reasonably stable managed infrastructure like PlanetLab, there can be a high rate of effective node failure due to nodes becoming extremely slow suddenly and unpredictably. In this paper, we study how to reduce the churn rate itself.
Title
Minimizing Churn in Distributed Systems
Published
2005-11-12
Full Collection Name
Electrical Engineering & Computer Sciences Technical Reports
Other Identifiers
EECS-2005-12
Type
Text
Extent
13 p
Archive
The Engineering Library
Usage Statement
Researchers may make free and open use of the UC Berkeley Library’s digitized public domain materials. However, some materials in our online collections may be protected by U.S. copyright law (Title 17, U.S.C.). Use or reproduction of materials protected by copyright beyond that allowed by fair use (Title 17, U.S.C. § 107) requires permission from the copyright owners. The use or reproduction of some materials may also be restricted by terms of University of California gift or purchase agreements, privacy and publicity rights, or trademark law. Responsibility for determining rights status and permissibility of any use or reproduction rests exclusively with the researcher. To learn more or make inquiries, please see our permissions policies (https://www.lib.berkeley.edu/about/permissions-policies).
