Multi-Active Database Sync Loopback Control Using Source Tags
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Multi-active database synchronization can lead to loopback errors, such as duplicated key errors, due to endless synchronization cycles when data is synchronized between multiple active database instances.
Innovation Solution
Implementing a synchronization tag field and a synchronization time field in incremental datasets to track the source and timestamp of data, allowing the synchronization service to avoid loopbacks by checking these fields before synchronizing data between database instances.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data synchronization is implemented between multiple active database instances, then data availability and consistency are improved, but loopback errors such as duplicated key errors occur due to endless synchronization cycles
Solution Approach 1:
The patent applies preliminary action by adding synchronization tags and timestamps to data records before they are synchronized between database instances. This preliminary marking allows the synchronization service to identify and prevent loopback synchronization cycles in advance, avoiding duplicated key errors while maintaining data consistency across multiple active instances.
Solution Approach 2:
The patent implements feedback by using synchronization tags and timestamps as control mechanisms that provide information about the synchronization history of data records. The synchronization service uses this feedback information to determine whether a record should be synchronized, thereby preventing endless synchronization cycles and loopback errors while ensuring reliable data consistency.
2Reliability
If synchronization tags and timestamps are added to track data source and timing, then loopback control is improved, but device complexity increases
Solution Approach 1:
The patent applies parameter changes by modifying the data record structure to include synchronization tags and timestamps as new parameters. These additional parameters provide the necessary information for loopback control without fundamentally changing the synchronization mechanism, thereby improving reliability while keeping the increase in complexity manageable.
Data Source
AI summary
Systems and methods of loopback control in multi-active database synchronization are provided. A first database instance and a second database instance are configured with two-way synchronization. A synchronization tool detects a first log change in a first operation log associated with the first database instance. The first log change includes a first operation entry associated with a first data operation on a first data record in the first database instance. The first data record includes a first synchronization tag field comprising a first source tag representing a first data source associated with the first data operation on the first data record. If the source tag contains the identification of the second database instance, the synchronization tool skips the first operation entry, without synchronizing the first data operation to the second database instance to avoid data loopback.