GFS: The Google File System

More documents

Recommendations

Info

GFS: Consistency Model (2) • Changes to data are ordered as chosen by a primary – All replicas will be consistent – But multiple writes from the same client may be interleaved or overwritten by concurrent operations from other clients • Record append completes at least once, at offset of GFS’s choosing – Applications must cope with possible duplicates 22
GFS: Data Mutation Consistency Write Record Append serial success concurrent success failure defined consistent but undefined defined interspersed with inconsistent inconsistent 23
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 24 and 25: Applications and Record Append Sema
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?