Lock Server Cluster Recovery Without Synchronous Lock Replication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Distributed transaction processing in distributed systems incurs high performance overheads due to synchronous duplication of lock data between primary and secondary nodes, affecting efficiency.
Innovation Solution
A distributed transaction processing method and system that utilizes a lock server cluster to manage lock requests without backing up lock data on secondary nodes, using a transaction coordinator list synchronized by a primary lock server to ensure efficient recovery in case of faults.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If lock data is synchronously duplicated from primary node to secondary node, then reliability is improved, but performance overhead increases
Solution Approach 1:
The patent uses asynchronous copying of lock data from primary node to secondary node instead of synchronous copying. The primary node sends lock data to secondary nodes asynchronously, allowing the primary node to continue processing without waiting for confirmation, thus reducing performance overhead while maintaining reliability through eventual consistency
Solution Approach 2:
The patent pre-establishes multiple secondary nodes that can serve as backup lock servers. When a primary node fails, the system can quickly switch to a pre-configured secondary node, improving reliability without requiring real-time synchronization during normal operation
2Reliability
If lock data is synchronously duplicated between primary and secondary nodes, then data consistency is improved, but processing delay increases
Solution Approach 1:
The patent implements periodic asynchronous synchronization where secondary nodes periodically request and receive lock data from the primary node, rather than requiring immediate synchronous confirmation. This periodic action maintains data consistency over time while avoiding the processing delays of synchronous operations
Solution Approach 2:
The patent uses asynchronous copying mechanisms where the primary node sends lock data to secondary nodes without waiting for acknowledgment. This allows the primary node to proceed with transaction processing immediately, reducing processing delay while still maintaining data consistency through the asynchronous replication process
3Reliability
If lock data is backed up on secondary nodes, then reliability is improved, but device complexity increases
Solution Approach 1:
The patent segments the lock server functionality by designating specific nodes as primary lock servers and others as secondary lock servers. Each node has a clearly defined role, with primary nodes handling active lock management and secondary nodes serving as backups. This segmentation improves reliability through redundancy while keeping the system structure simple and manageable
Solution Approach 2:
The patent creates simplified copies of lock data on secondary nodes without requiring full functional duplication. Secondary nodes store lock data and can take over if the primary fails, but don't need to maintain the same level of complexity as primary nodes, thus improving reliability while minimizing the increase in device complexity
Data Source
AI summary
A method includes a first lock server in a lock server cluster sending, based on a transaction coordinator list, a request for obtaining lock data to each transaction coordinator in a transaction coordinator list. If the lock data sent by each transaction coordinator in the transaction coordinator list is obtained, the first lock server processes a lock request sent by the transaction coordinator in the transaction coordinator cluster.