Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.
Google File System
Transcript of Google File System
Once written, files are seldom modified again.
Small writes at arbitrary positions in a file are supported but do not have to be efficient. The system must efficiently implement well-defined semantics for multiple clients that concurrently append to the same file. Atomicity with minimal synchronization overhead is essential. Provide a familiar file system interface Files are organized hierarchically in directories and identified by pathnames Snapshot operation to create a copy of a file or a directory tree at low cost Record append operation to allow multiple clients to append data to the same file concurrently while guaranteeing the atomicity of each individual client’s append Expected to run on commodity Linux machines running a user-level server process Single master and multiple chunkserver architecture Master maintains all filesystem metadata and coordinates system-wide activities Chunkservers store chunks of data on local disks as Linux files Files are divided into fixed-size chunks Data is replicated by a configured factor (x3 by default) Clients interact with the master for metadata operations, but all data-bearing communications go directly to the chunkservers