TY - GEN
T1 - Optimistic transactional active replication
AU - Horii, Hiroshi
AU - Yamana, Hayato
PY - 2008
Y1 - 2008
N2 - Critical database applications require 2-safe replication between at least two sites for disaster-tolerant services. At the same time, they must provide consistent and low-latency results to their clients in normal cases. In this paper, we propose Optimistic Transactional Active Replication (OTAR), which replicates the transaction logs with low latency and provides a consistent view to database applications. The latency of our replication is lower than Passive Replication, and guarantees the serializability of transaction isolation levels that cannot be supported by Active Replication. For our replication, each client sends a transaction request to all replicas and all of the replicas execute the request and optimistically return the result of the transaction to the client. Each replica generates a causality history of the transaction, sent to the client with the result. With the causality histories, the client can make sure that the requested transaction was executed in the same order at all of the replicas and eventually commit it. If the client cannot validate the order, then the client waits for the pessimistic result of the transaction from the replicas. This paper describes the algorithm and its properties.
AB - Critical database applications require 2-safe replication between at least two sites for disaster-tolerant services. At the same time, they must provide consistent and low-latency results to their clients in normal cases. In this paper, we propose Optimistic Transactional Active Replication (OTAR), which replicates the transaction logs with low latency and provides a consistent view to database applications. The latency of our replication is lower than Passive Replication, and guarantees the serializability of transaction isolation levels that cannot be supported by Active Replication. For our replication, each client sends a transaction request to all replicas and all of the replicas execute the request and optimistically return the result of the transaction to the client. Each replica generates a causality history of the transaction, sent to the client with the result. With the causality histories, the client can make sure that the requested transaction was executed in the same order at all of the replicas and eventually commit it. If the client cannot validate the order, then the client waits for the pessimistic result of the transaction from the replicas. This paper describes the algorithm and its properties.
KW - disaster tolerant
KW - replication
KW - transaction
UR - http://www.scopus.com/inward/record.url?scp=79959347200&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=79959347200&partnerID=8YFLogxK
U2 - 10.1145/1352793.1352813
DO - 10.1145/1352793.1352813
M3 - Conference contribution
AN - SCOPUS:79959347200
SN - 9781595939937
T3 - Proceedings of the 2nd International Conference on Ubiquitous Information Management and Communication, ICUIMC-2008
SP - 94
EP - 100
BT - Proceedings of the 2nd International Conference on Ubiquitous Information Management and Communication, ICUIMC-2008
T2 - 2nd International Conference on Ubiquitous Information Management and Communication, ICUIMC-2008
Y2 - 31 January 2008 through 1 February 2008
ER -