Google File System论文阅读

google file system

Q&A

  • Why is atomic record append at-least-once, rather than exactly once?

  • How does an application know what sections of a chunk consist of padding and duplicate records?

  • How can clients find their data given that atomic record append writes it at an unpredictable offset in the file?

  • The paper mentions reference counts -- what are they?

  • If an application uses the standard POSIX file APIs, would it need to be modified in order to use GFS?

  • How does GFS determine the location of the nearest replica?

  • Does Google still use GFS?

  • Won't the master be a performance bottleneck?

  • How acceptable is it that GFS trades correctness for performance and simplicity?

  • What if the master fails?

posted @ 2019-05-21 09:42  御心飞行  阅读(221)  评论(0)  编辑  收藏  举报