GFS: The Google File System

More documents

Recommendations

Info

Applications and Record Append Semantics • Applications should use self-describing records and checksums when using Record Append – Reader can identify padding / record fragments • If application cannot tolerate duplicated records, should include unique ID in record – Reader can use unique IDs to filter duplicates 24
Logging at Master • Master has all metadata information – Lose it, and you’ve lost the filesystem! • Master logs all client requests to disk sequentially • Replicates log entries to remote backup servers • Only replies to client after log entries safe on disk on self and backups! 25
Page 1 and 2: GFS: The Google File System Michael
Page 5 and 6: Google Platform Characteristics •
Page 8 and 9: Google File System: Design Criteria
Page 10 and 11: GFS: Architecture (2) 10
Page 12 and 13: Chunkserver • Stores 64 MB file c
Page 14 and 15: Client API • Not a filesystem in
Page 16 and 17: Client Write • Some chunkserver i
Page 18 and 19: Client Write (3) • All replicas a
Page 20 and 21: Client Record Append (2) • When d
Page 22 and 23: GFS: Consistency Model (2) • Chan
Page 26 and 27: Chunk Leases and Version Numbers
Page 28 and 29: What if Chunkserver Fails? • Mast
Page 30: Limitations • Security? - Trusted
Page 37: Recovery Time • Experiment: kille

GFS: The Google File System

Create successful ePaper yourself

Delete template?

Save as template?