17.6. Crashes
In Chapter 15 we considered the effects of crashes and mechanisms that would provide crash resilience for a single operation invocation. Figure 17.6 reiterates the basic approach. In Chapter 16 we considered an operation on one host being invoked from another host in a distributed system and considered the possibility of crashes both in the invoking and invoked systems. We now generalize these ideas.
Figure 17.6. A potentially atomic operation invocation.
Suppose, in the simple example introduced in Section 17.5 above, that a crash occurs after the debit operation, which must have written its result to persistent store in order to ...
Get Operating Systems: Concurrent and Distributed Software Design now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
