Skip to content

Latest commit

 

History

History

LEC03

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
6.824 Lab 2: Raft_files
6.824 Lab 2: Raft_files
 
 
6.824 Lab 2: Raft.html
6.824 Lab 2: Raft.html
 
 
Bolosky.pdf
Bolosky.pdf
 
 
README.md
README.md
 
 
gfs-faq.txt.md
gfs-faq.txt.md
 
 
gfs.pdf
gfs.pdf
 
 
l-gfs-short.txt.md
l-gfs-short.txt.md
 
 
raft-extended.pdf
raft-extended.pdf
 
 
raft-locking.txt.md
raft-locking.txt.md
 
 
raft-structure.txt.md
raft-structure.txt.md
 
 

README.md

课程 03

课前思考

阅读论文 GFS(2003)，可以思考以下问题:

  1. Why is atomic record append at-least-once, rather than exactly once?
  2. How does an application know what sections of a chunk consist of padding and duplicate records?
  3. How can clients find their data given that atomic record append writes it at an unpredictable offset in the file?
  4. The paper mentions reference counts -- what are they?
  5. If an application uses the standard POSIX file APIs, would it need to be modified in order to use GFS?
  6. How does GFS determine the location of the nearest replica?
  7. Does Google still use GFS?
  8. Won't the master be a performance bottleneck?
  9. How acceptable is it that GFS trades correctness for performance and simplicity?
  10. What if the master fails?

问题的答案在这里

在阅读讲义请先思考以下问题：

  • Why are we reading this paper?
  • What is consistency?
  • "Ideal" consistency model
  • Challenges to achieving ideal consistency
  • GFS goals:
  • High-level design / Reads / Writes
  • Record append
  • Housekeeping
  • Failures
  • Does GFS achieve "ideal" consistency?
  • Authors claims weak consistency is not a big problems for apps
  • Performance (Figure 3)

Lab 02

[Lab 02 的上机说明](6.824 Lab 2: Raft.html)

Lab 02 准备工作