1 cse232a: database system principles notes 08: failure recovery
TRANSCRIPT
![Page 1: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/1.jpg)
1
CSE232A: Database System Principles
Notes 08: Failure Recovery
![Page 2: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/2.jpg)
2
Integrity or correctness of data
• Would like data to be “accurate” or“correct” at all times
EMP Name
WhiteGreenGray
Age
523421
1
![Page 3: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/3.jpg)
3
Integrity or consistency constraints• Predicates data must satisfy• Examples:
- x is key of relation R- x y holds in R- Domain(x) = {Red, Blue, Green}is valid index for attribute x of R- no employee should make more than
twice the average salary
![Page 4: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/4.jpg)
4
Definition:
• Consistent state: satisfies all constraints
• Consistent DB: DB in consistent state
![Page 5: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/5.jpg)
5
Constraints (as we use here) may not capture “full
correctness”Example 1 Transaction constraints• When salary is updated,
new salary > old salary• When account record is deleted,
balance = 0
![Page 6: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/6.jpg)
6
Note: could be “emulated” by simpleconstraints, e.g.,
accountAcct # …. balancedeleted?
![Page 7: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/7.jpg)
7
Example 2 Database should reflect real world
DBReality
Constraints (as we use here) may not capture “full
correctness”
![Page 8: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/8.jpg)
8
in any case, continue with constraints...Observation: DB cannot be consistent
always!Example: a1 + a2 +…. an = TOT (constraint)
Deposit $100 in a2: a2 a2 + 100TOT TOT + 100
![Page 9: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/9.jpg)
9
a2
TOT
.
.50
.
.1000
.
.150
.
.1000
.
.150
.
.1100
Example: a1 + a2 +…. an = TOT (constraint)Deposit $100 in a2: a2 a2 + 100
TOT TOT + 100
![Page 10: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/10.jpg)
10
Transaction: collection of actions
that preserve consistency
Consistent DB Consistent DB’T
![Page 11: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/11.jpg)
11
Big assumption:
If T starts with consistent state + T executes in isolation
T leaves consistent state
![Page 12: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/12.jpg)
12
Correctness (informally)
• If we stop running transactions,DB left consistent
• Each transaction sees a consistent DB
![Page 13: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/13.jpg)
13
How can constraints be violated?
• Transaction bug• DBMS bug• Hardware failure
e.g., disk crash alters balance of account
• Data sharinge.g.: T1: give 10% raise to programmers
T2: change programmers systems analysts
![Page 14: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/14.jpg)
14
How can we prevent/fix violations?
• Chapter 8: due to failures only• Chapter 9: due to data sharing
only• Chapter 10: due to failures and
sharing
![Page 15: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/15.jpg)
15
Will not consider:
• How to write correct transactions• How to write correct DBMS• Constraint checking & repair
That is, solutions studied here do not need
to know constraints
![Page 16: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/16.jpg)
16
Chapter 8 Recovery
• First order of business:Failure Model
![Page 17: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/17.jpg)
17
Events Desired Undesired Expected
Unexpected
![Page 18: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/18.jpg)
18
Our failure model
processor
memory disk
CPU
M D
![Page 19: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/19.jpg)
19
Desired events: see product manuals….
Undesired expected events:System crash
- memory lost- cpu halts, resets
Undesired Unexpected: Everything else!
that’s it!!
![Page 20: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/20.jpg)
20
Examples:• Disk data is lost• Memory lost without CPU halt• CPU implodes wiping out universe….
Undesired Unexpected: Everything else!
![Page 21: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/21.jpg)
21
Is this model reasonable?
Approach: Add low level checks + redundancy to increase
probability model holds
E.g., Replicate disk storage (stable store)
Memory parity CPU checks
![Page 22: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/22.jpg)
22
Second order of business:
Storage hierarchy
Memory Disk
x x
![Page 23: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/23.jpg)
23
Operations:
• Input (x): block with x memory• Output (x): block with 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
![Page 24: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/24.jpg)
24
Key problem Unfinished transaction
Example Constraint: A=B T1: A A 2 B B 2
![Page 25: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/25.jpg)
25
T1: Read (A,t); t t2Write (A,t);Read (B,t); t t2Write (B,t);Output (A);Output (B);
A: 8B: 8
A: 8B: 8
memory disk
1616
16
failure!
![Page 26: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/26.jpg)
26
• Need atomicity: execute all actions of a transaction or none at all
![Page 27: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/27.jpg)
27
One solution: undo logging (immediate
modification)
due to: Hansel and Gretel, 782 AD
• Improved in 784 AD to durable undo logging
![Page 28: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/28.jpg)
28
T1: Read (A,t); t t2 A=B
Write (A,t);Read (B,t); t t2Write (B,t);Output (A);Output (B);
A:8B:8
A:8B:8
memory disk log
Undo logging (Immediate modification)
1616
<T1, start><T1, A, 8>
<T1, commit>16 <T1, B, 8>
16
![Page 29: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/29.jpg)
29
One “complication”
• Log is first written in memory• Not written to disk on every action
memory
DB
Log
A: 8 16B: 8 16Log:<T1,start><T1, A, 8><T1, B, 8>
A: 8B: 8
16BAD STATE
# 1
![Page 30: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/30.jpg)
30
One “complication”
• Log is first written in memory• Not written to disk on every action
memory
DB
Log
A: 8 16B: 8 16Log:<T1,start><T1, A, 8><T1, B, 8><T1, commit>
A: 8B: 8
16BAD STATE
# 2
<T1, B, 8><T1, commit>
...
![Page 31: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/31.jpg)
31
Undo logging rules
(1) For every action generate undo logrecord (containing old value)
(2) Before x is modified on disk, logrecords pertaining to x must beon disk (write ahead logging:
WAL)(3) Before commit is flushed to log, all
writes of transaction must bereflected on disk
![Page 32: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/32.jpg)
32
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??
![Page 33: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/33.jpg)
33
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:
- if Ti S then - write (X, v)
- output (X)
(3) For each Ti S do
- write <Ti, abort> to log
![Page 34: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/34.jpg)
34
What if failure during recovery?No problem! Undo idempotent
![Page 35: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/35.jpg)
35
To discuss:
• Redo logging• Undo/redo logging, why both?• Real world actions• Checkpoints• Media failures
![Page 36: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/36.jpg)
36
Redo logging (deferred modification)
T1: Read(A,t); t t2; write (A,t); Read(B,t); t t2; write (B,t);
Output(A); Output(B)
A: 8B: 8
A: 8B: 8
memory DB LOG
1616
<T1, start><T1, A, 16><T1, B, 16>
<T1, commit>
output16
![Page 37: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/37.jpg)
37
Redo logging rules
(1) For every action, generate redo logrecord (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
![Page 38: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/38.jpg)
38
• For every Ti with <Ti, commit> in log:– For all <Ti, X, v> in log:
Write(X, v)Output(X)
Recovery rules: Redo logging
IS THIS CORRECT??
![Page 39: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/39.jpg)
39
(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)
optional
Recovery rules: Redo logging
![Page 40: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/40.jpg)
40
Recovery is very, very
SLOW !Redo log:
First T1 wrote A,B LastRecord Committed a year ago
Record(1 year ago) --> STILL, Need to redo after crash!!
... ... ...
Crash
![Page 41: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/41.jpg)
41
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
![Page 42: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/42.jpg)
42
Example: what to do at recovery?
Redo log (disk):
<T1
,A,1
6>
<T1
,com
mit
>
Ch
eck
poin
t
<T2
,B,1
7>
<T2
,com
mit
>
<T3
,C,2
1>
Crash... ... ... ...
...
...
![Page 43: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/43.jpg)
43
Key drawbacks:
• Undo logging: cannot bring backup DBcopies up to date
• Redo logging: need to keep all modified blocks inmemory
until commit
![Page 44: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/44.jpg)
44
Solution: undo/redo logging!
Update <Ti, Xid, New X val, Old X val>page X
![Page 45: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/45.jpg)
45
Rules
• Page X can be flushed before orafter Ti commit
• Log record flushed before corresponding updated page (WAL)
• Flush at commit (log only)
![Page 46: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/46.jpg)
46
Non-quiesce checkpoint
LOG
for undo dirty buffer
pool pagesflushed
Start-ckptactive TR:
Ti,T2,...
endckpt
.........
...
![Page 47: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/47.jpg)
47
Examples what to do at recovery time?
no T1 commit
LOG
T1,-a
...CkptT1
...Ckptend
...T1-b
...
Undo T1 (undo a,b)
![Page 48: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/48.jpg)
48
Example
LOG
...T1
a... ...
T1
b... ...
T1
c...
T1
cmt...
ckpt-end
ckpt-sT1
Redo T1: (redo b,c)
![Page 49: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/49.jpg)
49
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
backward pass
forward passstart
check-point
![Page 50: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/50.jpg)
50
Real world actions
E.g., dispense cash at ATMTi = a1 a2 …... aj …... an
$
![Page 51: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/51.jpg)
51
Solution
(1) execute real-world actions after commit
(2) try to make idempotent
![Page 52: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/52.jpg)
52
ATMGive$$(amt, Tid, time)
$
give(amt)
lastTid:
time:
![Page 53: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/53.jpg)
53
Media failure (loss of non-volatile storage)
A: 16
Solution: Make copies of data!
![Page 54: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/54.jpg)
54
Example 1 Triple modular redundancy
• Keep 3 copies on separate disks• Output(X) --> three outputs• Input(X) --> three inputs + vote
X1 X2 X3
![Page 55: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/55.jpg)
55
Example #2 Redundant writes, Single reads
• Keep N copies on separate disks• Output(X) --> N outputs• Input(X) --> Input one copy
- if ok, done- else try
another one Assumes bad data can be detected
![Page 56: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/56.jpg)
56
Example #3: DB Dump + Log
backupdatabase
activedatabase
log
• If active database is lost,– restore active database from backup– bring up-to-date using redo entries in log
![Page 57: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/57.jpg)
57
When can log be discarded?
check-point
dbdump
lastneededundo
not needed formedia recovery
not needed for undoafter system failure
not needed forredo after system failure
log
time
![Page 58: 1 CSE232A: Database System Principles Notes 08: Failure Recovery](https://reader035.vdocuments.us/reader035/viewer/2022062517/56649ef05503460f94c00732/html5/thumbnails/58.jpg)
58
Summary
• Consistency of data• One source of problems: failures
- Logging- Redundancy
• Another source of problems: Data Sharing..... next