Data Replication Transaction Log Request Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data replication systems face performance degradation due to synchronization delays when a node or communication path fails, leading to increased time for synchronization and decreased system performance.
Innovation Solution
Implement a method where a slave node requests a transaction log from a master node or parent node within specified times (Ts1 and Ts3) if no reply is received, and updates its replica database using the received transaction log, allowing for speedy synchronization and search operations even if communication issues occur.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If synchronization process is performed with all replica DBs whenever master DB is updated, then data consistency is maintained, but system performance decreases due to communication failures and time-consuming synchronization
Solution Approach 1:
The patent applies partial synchronization by selecting only a subset of replica DBs (those that responded within a predetermined time period) for the synchronization process, rather than forcing synchronization with all replica DBs. This allows the master node to complete updates without waiting for slow or failed nodes, thereby maintaining data consistency for the majority of replicas while preserving system performance and avoiding bottlenecks caused by communication failures.
2Reliability
If synchronization waits for all slave nodes to complete, then data consistency is ensured, but synchronization time increases when any node experiences communication delays
Solution Approach 1:
The system performs synchronization with only those slave nodes that complete their communication within a predetermined time period, rather than waiting for all nodes. This partial action approach ensures data consistency for the synchronized subset while avoiding the time loss associated with waiting for delayed or failed nodes, thus resolving the contradiction between consistency and synchronization time.
Solution Approach 2:
The master node establishes a predetermined time period for slave node responses before initiating the synchronization process. This preliminary time constraint allows the system to proactively identify and exclude slow or failed nodes from the synchronization wait, thereby reducing synchronization time while maintaining consistency for the responsive subset of replicas.
3Reliability
If transaction log is transferred to all slave nodes on every update, then data consistency is maintained, but communication overhead and processing time increase
Solution Approach 1:
The patent transfers transaction logs only to the subset of slave nodes that respond within the predetermined time period, rather than to all slave nodes. This partial transfer reduces communication overhead and processing complexity while maintaining data consistency for the synchronized replicas, effectively resolving the contradiction between consistency and device complexity.
Data Source
AI summary
Data replication management which enables rapid retrieval while increasing the performance of the entire system, and maintaining data synchronization regarding successively updated data is performed. There are steps which comprises a step that when a slave node which has received an instruction for retrieval does not receive a return massage from a master node within a predetermined time period (Ts1) from the transmission of a request message to the master node, the slave node requests the master node to provide a transaction log up to the latest version with respect to the update of a master database; a step that the master node which has received the request transmits the transaction log to the slave node; and a step that the slave node updates a replica database with reference to the transaction log transferred from the master node.