Scale and performance in a distributed file system
ACM Transactions on Computer Systems (TOCS)
Measurements of a distributed file system
SOSP '91 Proceedings of the thirteenth ACM symposium on Operating systems principles
Disconnected operation in the Coda File System
ACM Transactions on Computer Systems (TOCS)
The design and implementation of a log-structured file system
ACM Transactions on Computer Systems (TOCS)
Lightweight recoverable virtual memory
ACM Transactions on Computer Systems (TOCS) - Special issue on operating systems principles
An empirical study of a highly available file system
SIGMETRICS '94 Proceedings of the 1994 ACM SIGMETRICS conference on Measurement and modeling of computer systems
Exploiting weak connectivity for mobile file access
SOSP '95 Proceedings of the fifteenth ACM symposium on Operating systems principles
An empirical study of a wide-area distributed file system
ACM Transactions on Computer Systems (TOCS)
Flexible update propagation for weakly consistent replication
Proceedings of the sixteenth ACM symposium on Operating systems principles
A reliable multicast framework for light-weight sessions and application level framing
IEEE/ACM Transactions on Networking (TON)
Perspectives on optimistically replicated, peer-to-peer filing
Software—Practice & Experience
The design of a multicast-based distributed file system
OSDI '99 Proceedings of the third symposium on Operating systems design and implementation
File system usage in Windows NT 4.0
Proceedings of the seventeenth ACM symposium on Operating systems principles
Time, clocks, and the ordering of events in a distributed system
Communications of the ACM
OceanStore: an architecture for global-scale persistent storage
ASPLOS IX Proceedings of the ninth international conference on Architectural support for programming languages and operating systems
Deferring trust in fluid replication
EW 9 Proceedings of the 9th workshop on ACM SIGOPS European workshop: beyond the PC: new challenges for the operating system
Design and evaluation of a continuous consistency model for replicated services
OSDI'00 Proceedings of the 4th conference on Symposium on Operating System Design & Implementation - Volume 4
Flexible and safe resolution of file conflicts
TCON'95 Proceedings of the USENIX 1995 Technical Conference Proceedings
Hints for Computer System Design
IEEE Software
REDMAN: A Decentralized Middleware Solution for Cooperative Replication in Dense MANETs
PERCOMW '05 Proceedings of the Third IEEE International Conference on Pervasive Computing and Communications Workshops
ACM Computing Surveys (CSUR)
REDMAN: An optimistic replication middleware for read-only resources in dense MANETs
Pervasive and Mobile Computing
Generalization of the fast consistency algorithm to a grid with multiple high demand zones
ICCS'03 Proceedings of the 2003 international conference on Computational science: PartII
Hi-index | 0.00 |
Abstract: Mobile users can increasingly depend on high speed connectivity. Despite this, using distributed file services across the wide area is painful. Past approaches sacrifice one or more of safety, visibility, and consistency in the name of performance. Instead, we propose Fluid Replication, the ability to create replicas where and when needed. These replicas, called WayStations, maintain consistency with home servers through periodic reconciliations. Two techniques make reconciliation fast; this is crucial to the success of Fluid Replication. First, we defer propagation of updates, and only invalidate files during a reconciliation. Second, rather than depend on operation logs, we provide the subtrees in which all updates have occurred. These subtrees, named by their least common ancestors, or LCAs, can be constructed incrementally, and reduce the burden of checking serializability during a reconciliation. While these techniques provide better performance, they are not without risk. Bulk invalidation can lead to false sharing, optimistic updates are subject to conflict, and deferred updates may cause performance problems if they are needed elsewhere. To address these concerns, we performed a trace-based evaluation of our algorithms. Because reconciliations can be frequent, no update conflicts were produced. Less than 0.2% of all file operations required a spurious revalidation, and less than 4% of all updates were needed at remote sites, resulting in substantial performance benefits.