Oracle international corporation (20240126783). RECOVERY FROM LOSS OF LEADER DURING ASYNCHRONOUS DATABASE TRANSACTION REPLICATION simplified abstract

RECOVERY FROM LOSS OF LEADER DURING ASYNCHRONOUS DATABASE TRANSACTION REPLICATION

Organization Name

oracle international corporation

Inventor(s)

Lik Wong of Palo Alto CA (US)

Leonid Novak of Castro Valley CA (US)

Sampanna Salunke of San Carlos CA (US)

Mark Dilman of Sunnyvale CA (US)

Wei-Ming Hu of Palo Alto CA (US)

RECOVERY FROM LOSS OF LEADER DURING ASYNCHRONOUS DATABASE TRANSACTION REPLICATION - A simplified explanation of the abstract

This abstract first appeared for US patent application 20240126783 titled 'RECOVERY FROM LOSS OF LEADER DURING ASYNCHRONOUS DATABASE TRANSACTION REPLICATION

Simplified Explanation

The lead-sync log record is used to synchronize replication logs of follower shards to the leader shard in a distributed database system.

• The new leader shard performs a sync operation using the lead-sync log record to synchronize replication logs of follower shards to the replication log of the new leader after a failure to determine consensus for a database transaction commit operation.
• A recovery window is defined in the replication log to identify transactions to be recovered, and a recovery action is performed on the set of transactions to be recovered.

Potential Applications

This technology can be applied in distributed database systems, cloud computing environments, and any system requiring synchronization of replication logs.

Problems Solved

1. Ensures consistency and synchronization of replication logs in a distributed database system. 2. Facilitates recovery of transactions in case of failures or inconsistencies in the replication logs.

Benefits

1. Improved reliability and fault tolerance in distributed systems. 2. Simplified management of replication logs and recovery processes. 3. Enhanced data consistency and integrity across multiple shards.

Potential Commercial Applications

"Lead-Sync Log Record Synchronization for Distributed Systems" can be utilized in cloud service providers, e-commerce platforms, financial institutions, and any organization with distributed data storage needs.

Possible Prior Art

One possible prior art could be the use of distributed consensus algorithms like Paxos or Raft for log synchronization in distributed systems.

How does the lead-sync log record handle conflicts in replication logs during synchronization?

The article does not provide details on how conflicts in replication logs are resolved during the synchronization process. This could be an important aspect to consider for ensuring data consistency in distributed systems.

What is the impact of the recovery window size on the performance of the recovery action?

The article does not discuss the potential impact of the size of the recovery window on the efficiency and effectiveness of the recovery action. Understanding this relationship could help optimize the recovery process in distributed database systems.

Original Abstract Submitted

a lead-sync log record is used to synchronize the replication logs of follower shards to the leader shard. in response to a failure to determine that there is a consensus for a database transaction commit operation after a shard server becomes a new leader, the new leader shard performs a sync operation using the lead-sync log record to synchronize replication logs of the follower shards to the replication log of the new leader. a shard server identifies a first transaction having a first log record but not a post-commit log record in the replication log, defines a recovery window in the replication log starting at the first log record of the identified first transaction and ending at the lead-sync log record, identifies a set of transactions to be recovered, and performs a recovery action on the set of transactions to be recovered.