GFS: The Google File System

More documents

Recommendations

Info

Client Record Append (2) • When data won’t fit in last chunk: – Primary fills current chunk with padding – Primary instructs other replicas to do same – Primary replies to client, “retry on next chunk” • If record append fails at any replica, client retries operation – So replicas of same chunk may contain different data —even duplicates of all or part of record data • What guarantee does <strong>GFS</strong> provide on success? – Data written at least once in atomic unit 20
<strong>GFS</strong>: Consistency Model • Changes to namespace (i.e., metadata) are atomic – Done by single master server! – Master uses log to define global total order of namespace-changing operations 21
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 22 and 23: GFS: Consistency Model (2) • Chan
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?