TY - GEN
T1 - TRANSACTION RECOVERY IN DISTRIBUTED DB/DC SYSTEMS
T2 - A PROGRESSIVE APPROACH.
AU - Yu, Philip S.
AU - Iyer, Balakrishna R.
AU - Lee, Yann Hang
PY - 1986/1/1
Y1 - 1986/1/1
N2 - Focus is on recovery of transactions in a distributed DB/DC system. The objective is to use transaction-level structural information to eliminate costly lower-level handshaking protocols, eliminate the need for any centralized recovery management mechanism by making recovery actions local to interacting components, and eliminate propagation of recovery actions to more than one antecedent or precedent component. Progressive recovery is a way of tracking the progress of a transaction to meet the above objective. Transaction processing involves different execution stages (DC, DB, followed by the DC), perhaps on different processors. Some stages make database changes and others are purely transformations of messages. The latter permit re-executions without side effects. The former must be well protected from re-executions. In contrast with optimistic recovery schemes, progressive recovery does not track communication and state dependencies.
AB - Focus is on recovery of transactions in a distributed DB/DC system. The objective is to use transaction-level structural information to eliminate costly lower-level handshaking protocols, eliminate the need for any centralized recovery management mechanism by making recovery actions local to interacting components, and eliminate propagation of recovery actions to more than one antecedent or precedent component. Progressive recovery is a way of tracking the progress of a transaction to meet the above objective. Transaction processing involves different execution stages (DC, DB, followed by the DC), perhaps on different processors. Some stages make database changes and others are purely transformations of messages. The latter permit re-executions without side effects. The former must be well protected from re-executions. In contrast with optimistic recovery schemes, progressive recovery does not track communication and state dependencies.
UR - http://www.scopus.com/inward/record.url?scp=0022579127&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=0022579127&partnerID=8YFLogxK
M3 - Conference contribution
AN - SCOPUS:0022579127
SN - 0818606908
T3 - Proceedings - Symposium on Reliability in Distributed Software and Database Systems
SP - 207
EP - 214
BT - Proceedings - Symposium on Reliability in Distributed Software and Database Systems
PB - IEEE
ER -