Topic:
updating information in a distributed system
Topic:
updating information with rumor mongering and random updates
Topic:
optimistic update for concurrency control
| |
Summary
Grapevine and Clearinghouse are early examples of name directory servers. They guaranteed that distributed information was eventually consistent.
Servers broadcasted updates and periodically verified consistency. See also rumor mongering. (cbb 8/06)
Subtopic: eventual consistency 
| Quote: Grapevine guarantees eventual consistency [»birrAD4_1982]
| | Quote: Clearinghouse guarantees that information is eventually consistent and correct [»oppeDC7_1983]
| | Quote: data (hints) stored by Clearinghouse may be inconsistent or incorrect [»oppeDC7_1983]
| | Quote: Grapevine's update algorithm does not bother users and allows a partitioned internet [»birrAD4_1982]
|
Subtopic: broadcast updates
| Quote: Clearinghouse servers broadcast update requests to their siblings [»oppeDC7_1983]
| | Quote: Clearinghouse's set of names allows simultaneous updates [»oppeDC7_1983]
|
Subtopic: timestamp updates
| Quote: Clearinghouse uses timestamps to detect subsumed update requests [»oppeDC10_1981]
| | Quote: Clearinghouse discards requests if subsumed or if all siblings are consistent [»oppeDC10_1981]
|
Subtopic: resolving inconsistencies
| Quote: in Clearinghouse, periodically compare databases in case broadcast fails [»oppeDC10_1981]
| | Quote: Clearinghouse assumes inconsistent requests are due to lost or late requests [»oppeDC10_1981]
| | Quote: Clearinghouse updates last a week -- long-down servers re-initialize themselves [»oppeDC10_1981]
|
Related Topics
Topic: updating information in a distributed system (50 items)
Topic: updating information with rumor mongering and random updates (13 items)
Topic: optimistic update for concurrency control
(35 items)
|
