coda - Disconnected Operations in CODA File System...

Info icon This preview shows pages 1–14. Sign up to view the full content.

View Full Document Right Arrow Icon
Disconnected Operations in CODA File System Presentation By : CG www.powerpointpresentationon.blogspot.com
Image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
CODA File System Developed for Distributed Machines Used in Disconnected Operations Environment Based on AFS (Andrew File System) Developed in UNIX Environment Replicates server for high availability Uses Cache Management for high availability
Image of page 2
Motivation
Image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Mechanisms to Increase Availability Server Replication Managing Disconnected Operations using Venus Updating Server When Disconnection ends Replica Updating after Disconnection
Image of page 4
An Example
Image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
An Example
Image of page 6
An Example
Image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
An Example
Image of page 8
An Example
Image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
An Example
Image of page 10
Design Rationale Scalability Whole-file caching Placing burden on Clients rather than Servers Avoidance of System wide changes Portable Workstations They are moving Have selective usage of File Users can predict their disconnection in most cases
Image of page 11

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Design Rationale (contd…) First Vs. Second Class Replication First Class replicas reside on Server, That are reliable, clean, available & complete. Second Class replica reside on Clients, That are inferior to all above dimensions. Cache Coherence protocol is used to synchronize both type of replica. Degraded second class replica is modified after reconnection. CODA also support sole server use of replica in case of performance & cost related issues.
Image of page 12
Design Rationale (contd…) Pessimistic Vs. Optimistic Replica Control
Image of page 13

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 14
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern