CS4432: Database Systems II
Lecture #24
Crash Recovery (chap 17)
Professor Elke A. Rundensteiner
cs4432
recovery
1
How can we prevent / fix violations?
• Chapter 8[17]: due to failures only
• Chapter 9[18]: due to data sharing only
• Chapter 10[19]: due to failures and sharing
cs4432
recovery
2
Chapter 8 [17]: Recovery
• First :
cs4432
Failure Model
recovery
3
Events
cs4432
Desired
Undesired
recovery
Expected
Unexpected
4
Our failure model
processor
CPU
memory
cs4432
M
D
recovery
disk
5
Desired events: see product manuals….
Undesired expected events:
System crash
- memory lost
- cpu halts, resets
that’s it!!
Undesired Unexpected:
cs4432
recovery
Everything else!
6
Undesired Unexpected:
Everything else!
Examples:
• Disk data is lost
• Memory lost without CPU halt
• CPU implodes wiping out universe….
cs4432
recovery
7
Operations re
Storage Hierarchy:
x
Memory
x
Disk
• Input (x): block containing x  memory
• Output (x): block containing x  disk
• Read (x,t): do input(x) if necessary
t  value of x in block
• Write (x,t): do input(x) if necessary
value of x in block  t
cs4432
recovery
9
Key problem : Unfinished transaction
Example:
cs4432
Constraint: A=B
T1: A  A  2
B  B2
recovery
10
T1: Read (A,t); t  t2
Write (A,t);
Read (B,t); t  t2
Write (B,t);
Output-to-Disk (A);
Output-to-Disk (B);failure!
A: 8 16
B: 8 16
A: 8 16
B: 8
memory
cs4432
disk
recovery
11
• Need atomicity:
execute all actions of a
transaction, or none at all
cs4432
recovery
12
One solution: undo logging
(immediate
modification)
A la Hansel and Gretel recording their
navigation through forest via bread
crumbs …
Must have durable undo logging !!!
cs4432
recovery
13
Undo logging
(Immediate modification)
T1: Read (A,t); t  t2
Write (A,t);
Read (B,t); t  t2
Write (B,t);
Output-to-disk (A);
Output-to-disk (B);
A:8 16
B:8 16
A:8 16
B:8 16
disk
memory
cs4432
recovery
A=B
<T1, start>
<T1, A, 8>
<T1, B, 8>
<T1, commit>
log
14
One “complication” : First disk, then log
• Log is first written in memory
• Not written to disk on every action
memory
A: 8 16
B: 8 16
Log:
<T1,start>
<T1, A, 8>
<T1, B, 8>
cs4432
A: 8 16
B: 8
DB
BAD STATE
#1
Log
recovery
15
One “complication” : first log, then disk.
• Log is first written in memory
• Not written to disk on every action
A: 8 16
B: 8 16
Log:
<T1,start>
<T1, A, 8>
<T1, B, 8>
<T1, commit>
cs4432
A: 8 16
B: 8
DB
Log
BAD STATE
#2
...
memory
<T1, B, 8>
<T1, commit>
recovery
16
Undo logging rules
(1) For every action generate undo log record
(containing old value)
(2) Before x is modified on disk,
log records pertaining to x must be
on disk first (write ahead logging)
(3) Before commit is written to log on disk,
all writes of transaction must be
reflected on disk
cs4432
recovery
17
Recovery rules:
Undo logging
• For every Ti with <Ti, start> in log:
- If <Ti,commit> or <Ti,abort>
in log, do nothing
- Else For all <Ti, X, v> in log:
write (X, v)
output (X )
Write <Ti, abort> to log
IS THIS CORRECT??
cs4432
recovery
18
Recovery rules:
Undo logging
(1) Let S = set of transactions with
<Ti, start> in log, but no
<Ti, commit> (or <Ti, abort>) record in log
(2) For each <Ti, X, v> in log,
in reverse order (latest  earliest) do:
- write old value from log back to disk:
- if Ti  S then - write (X, v)
- output (X)
(3) For each Ti  S do
- write <Ti, abort> to log
cs4432
recovery
19
What if failure during recovery?
No problem!  Undo idempotent
cs4432
recovery
20
To discuss next :
• Redo logging
• Checkpoints
• Undo/redo logging, why both?
cs4432
recovery
21
Redo logging (deferred modification)
T1: Read(A,t); t t2; write (A,t);
Read(B,t); t t2; write (B,t);
Output(A); Output(B)
A: 8 16
B: 8 16
memory
cs4432
output
A: 8 16
B: 8
DB
recovery
<T1, start>
<T1, A, 16>
<T1, B, 16>
<T1, commit>
LOG
22
Redo logging rules
(1) For every action, generate redo log
record (containing new value)
(2) Before X is modified on disk (DB),
all log records for transaction that
modified X (including commit) must
be on disk
(3) Flush log at commit
cs4432
recovery
23
Recovery rules:
Redo logging
• Idea: Need to redo if transaction commit is in
log because we don’t know if transaction
failed or not.
• For every Ti with <Ti, commit> in log:
– For all <Ti, X, v> in log:
Write(X, v)
Output(X)
IS THIS CORRECT??
cs4432
recovery
24
Recovery rules:
Redo logging
(1) Let S = set of transactions with
<Ti, commit> in log
(2) For each <Ti, X, v> in log,
in forward order (earliest  latest) do:
- if Ti  S then Write(X, v)
Output(X)
cs4432
recovery
25
Recovery is very, very
SLOW !
Redo log:
...
First
Record
(1 year ago)
cs4432
...
...
T1 wrote A,B
Committed a year ago
--> STILL, Need to redo after crash!!
recovery
Last
Crash
Record
26
Solution: Checkpoint
(simple version)
Periodically:
(1) Do not accept new transactions
(2) Wait until all transactions finish
(3) Flush all log records to disk (log)
(4) Flush all buffers to disk (DB) (do not discard buffers)
(5) Write “checkpoint” record on disk (log)
(6) Resume transaction processing
cs4432
recovery
27
Example: what to do at recovery?
cs4432
recovery
...
<T3,C,21>
...
<T2,commit>
...
<T2,B,17>
...
Checkpoint
...
<T1,commit>
...
<T1,A,16>
Redo log (disk):
Crash
28
Key drawbacks:
• Undo logging: cannot bring backup DB
copies up to date
• Redo logging: need to keep all modified
blocks in memory
until commit
cs4432
recovery
29
Solution: undo/redo logging!
Combine Undo/Redo Logging, namely:
Update  <Ti, Xid, New X val, Old X val>
page X
cs4432
recovery
30
Rules
• Page X can be flushed before or
after Ti commit
• Log record flushed before
corresponding updated page (WAL)
• Flush at commit (log only)
cs4432
recovery
31
Non-quiesce checkpoint
L
O
G
...
end
ckpt
...
...
...
Start-ckpt
active TR:
Ti,T2,...
for
undo
cs4432
dirty buffer
pool pages
flushed
recovery
32
Examples what to do at recovery time?
no T1 commit
L
O
G
...
T1,a
 Undo T1
cs4432
...
Ckpt
T1
...
Ckpt
end
...
T 1b
(undo a,b)
recovery
33
Example
L
O
G
ckpt-s
T1
T1
ckptT1
T1
...
... T1 ...
...
...
...
...
a
b
end
c
cmt
 Redo T1: (redo b,c)
cs4432
recovery
34
Recovery process:
• Backwards pass
(end of log  latest checkpoint start)
– construct set S of committed transactions
– undo actions of transactions not in S
• Undo pending transactions
– follow undo chains for transactions in
(checkpoint active list) - S
• Forward pass
(latest checkpoint start  end of log)
– redo actions of S transactions
start
checkpoint
cs4432
backward pass
forward pass
recovery
35
Summary
• One source of problems: failures
• Solutions:
- Logging/Redundancy
cs4432
recovery
36