1998
DOI: 10.1002/(sici)1097-024x(199802)28:2<155::aid-spe155>3.0.co;2-5
|View full text |Cite
|
Sign up to set email alerts
|

Perspectives on optimistically replicated, peer-to-peer filing

Abstract: This research proposes and tests an approach to engineering distributed file systems that are aimed at wide-scale, Internet-based use. The premise is that replication is essential to deliver performance and availability, yet the traditional conservative replica consistency algorithms do not scale to this environment. Our Ficus replicated file system uses a single-copy availability, optimistic update policy with reconciliation algorithms that reliably detect concurrent updates and automatically restore the cons… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
43
0

Year Published

1998
1998
2008
2008

Publication Types

Select...
6
3
1

Relationship

1
9

Authors

Journals

citations
Cited by 58 publications
(43 citation statements)
references
References 26 publications
0
43
0
Order By: Relevance
“…There is substantial peer-to-peer work in the file system and OS literature that is relevant, including the Ficus [23], JetFile [13], Bayou [28] projects. All of them are replicated storage systems based on the peer-to-peer architecture.…”
Section: Related Workmentioning
confidence: 99%
“…There is substantial peer-to-peer work in the file system and OS literature that is relevant, including the Ficus [23], JetFile [13], Bayou [28] projects. All of them are replicated storage systems based on the peer-to-peer architecture.…”
Section: Related Workmentioning
confidence: 99%
“…Each replica obtains a quorum by gathering weighted votes from other replicas in the system and by providing its vote to others. Similarly, Coda [14] and Ficus [17] provide support for disconnected operations in the domain of distributed file systems. Each mobile device can modify its cached files while disconnected.…”
Section: Related Workmentioning
confidence: 99%
“…Typically, reconciliation takes place between two replicas. Updates are tracked using either logging [13] or scanning [10]. Conflicts occur when different replicas of the same file are updated after the most recent reconciliation.…”
Section: Introductionmentioning
confidence: 99%