Disconnected Operation in the Coda File System

Post on 05-Jan-2016

25 views 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 of Disconnected Operation in the Coda File System

Disconnected Operation in the Coda File System

姓名:吳佳憲學號: 491516262

Outline

MotivationAn ExampleDisconnected OperationDesign RationalePrioritized algorithm

Motivation

Disconnected Operation

Continue critical work when that repository is inaccessible.

Key idea: caching data. Performance Availability

Server Replication

An Example

An Example

An Example

An Example

An Example

An Example

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

Design Rationale -Replication

Server replication (why?)+ Persistent, Secure physically

- Expensive

Client replication- Low quality relatively

+Cheap

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

Implementation - architecture

Venus - states

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

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

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

Emulation

Act like a serverRecord modified objectsReplay update activity Preparation

Log based per volume

Persistence Meta-data RVM Exhaustion

Compress?

Conflict Handling

Only care write/write conflictionFile vs Directory

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

Conclusion

Doda is DFS with support for disconnected operation