19.9. Dealing with aborts: More about the property of isolation
The theory outlined above does not take into account that the operations of a transaction might be undone due to an abort termination. It must be possible to return the system to a consistent state as though the transaction had not taken place. The following problems could arise through concurrent execution of transactions, even if a serializable schedule of suboperations had been devised. It is demonstrated that serializability is necessary but not sufficient for correct concurrent operation.
19.9.1. Cascading aborts
Figure 19.13 shows a serializable schedule of the transactions T1 and T2 used above in Section 19.7. This time, T1 happens to abort.
Figure 19.13. Example of cascading ...
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.
