disconnected operation in the coda file system

21
Disconnected Operation in the Coda File System 姓姓 姓姓姓 姓姓491516262

Upload: kamuzu

Post on 05-Jan-2016

27 views

Category:

Documents


2 download

DESCRIPTION

Disconnected Operation in the Coda File System. 姓名:吳佳憲 學號: 491516262. Outline. Motivation An Example Disconnected Operatio n Design Rationale Prioritized algorithm. Motivation. Disconnected Operation. Continue critical work when that repository is inaccessible. Key idea: caching data. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Disconnected Operation in the Coda File System

Disconnected Operation in the Coda File System

姓名:吳佳憲學號: 491516262

Page 2: Disconnected Operation in the Coda File System

Outline

MotivationAn ExampleDisconnected OperationDesign RationalePrioritized algorithm

Page 3: Disconnected Operation in the Coda File System

Motivation

Page 4: Disconnected Operation in the Coda File System

Disconnected Operation

Continue critical work when that repository is inaccessible.

Key idea: caching data. Performance Availability

Server Replication

Page 5: Disconnected Operation in the Coda File System

An Example

Page 6: Disconnected Operation in the Coda File System

An Example

Page 7: Disconnected Operation in the Coda File System

An Example

Page 8: Disconnected Operation in the Coda File System

An Example

Page 9: Disconnected Operation in the Coda File System

An Example

Page 10: Disconnected Operation in the Coda File System

An Example

Page 11: Disconnected Operation in the Coda File System

Design Rationale

Scalability Callback cache coherence (inherit from AFS) Whole file caching Fat clients. (security, integrity) Avoid system-wide rapid change

Portable workstations User’s assistance in cache management

Page 12: Disconnected Operation in the Coda File System

Design Rationale -Replication

Server replication (why?)+ Persistent, Secure physically

- Expensive

Client replication- Low quality relatively

+Cheap

Page 13: Disconnected Operation in the Coda File System

Design Rationale –Replica Control

Pessimistic Disable all partitioned writes - Require a client to acquire control of a cached

object prior to disconnectionOptimistic

Assuming no others touching the file- sophisticated: conflict detection + fact: low write-sharing in Unix+ high availability: access anything in range

Page 14: Disconnected Operation in the Coda File System

Implementation - architecture

Page 15: Disconnected Operation in the Coda File System

Venus - states

Page 16: Disconnected Operation in the Coda File System

Hoarding

Hoard useful data for disconnectionBalance the needs of connected and

disconnected operation. Cache size is restricted Unpredictable disconnections

Prioritized algorithm – cache manage hoard walking – reevaluate objects

Page 17: Disconnected Operation in the Coda File System

Prioritized algorithm

User defined hoard priority p: how interest it is? Recent Usage q Object priority = f(p,q) Kick out the one with lowest priority

+ Fully tunableEverything can be customized

- Not tunable (?)- No idea how to customize

Page 18: Disconnected Operation in the Coda File System

Hoard Walking

Equilibrium – uncached obj < cached obj Why it may be broken? Cache size is limited.

Walking: restore equilibrium Reloading HDB (changed by others) Reevaluate priorities in HDB and cache Enhanced callback

Increase scalability, and availabilityDecrease consistency

Page 19: Disconnected Operation in the Coda File System

Emulation

Act like a serverRecord modified objectsReplay update activity Preparation

Log based per volume

Persistence Meta-data RVM Exhaustion

Compress?

Page 20: Disconnected Operation in the Coda File System

Conflict Handling

Only care write/write conflictionFile vs Directory

File: Halt entire reintegration process Dir: investigate more Manual repair

Page 21: Disconnected Operation in the Coda File System

Conclusion

Doda is DFS with support for disconnected operation