The reading for today is "High-availability computer systems" by Gray and Siewiorek, reading #33. This paper is another heavy duty paper; read it with care. In addition, read "The space shuttle primary computer system" by Spector and Gifford, reading #34. This paper is quite long; you can skim much of the paper, but as you do so slow down enough to figure out the following things: how are they using redundancy?, whatis force-fight voting?, and what are alibis?
In preparation, read Tanenbaum, Chapter 11, Section 4. This section covers transactions, which we will study in detail in this week. Read the section with care.
Read "The recovery manager of the system R database manager" by Gray et al., reading #35. This paper is another heavy duty paper, but contains important information, which is well explained. Read this paper with care. Since it is such an important paper, there will be a reading report due (sorry!). Here is the question:
System R uses a combination of logging and shadowing to provide robust, fault-tolerant transactions. What functions/guarantees does shadowing provide? logging?
No reading for today, finish up the paper on design project 2. It is due in tomorrow's section.
Read the Cirrus banking paper, reading #36, "The Cirrus banking network" by Gifford and Spector. This case study is shorter than the other two; you can skim it instead of giving it a detailed read. Also finish your design project, which is due in tomorrow's recitation section.
Your team's report on design project 2 is due today in section.
System aphorism of the week
Een schip op het strand is een baken in zee.
(A ship on the beach is a lighthouse on the sea.) (Dutch proverb)
6.033 Handout 35, issued 4/22/96