Multi-Active Database Loopback Control Using Source Tags
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-active database synchronization, loopback synchronization cycles can lead to errors such as duplicated key errors, which existing systems struggle to prevent effectively.
Innovation Solution
Implementing a synchronization tag field and a synchronization time field in incremental datasets to track the source and timing of data synchronization, allowing the synchronization service to detect and avoid loopbacks by checking these fields before synchronizing data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If database instances are replicated across multiple regions for high availability, then system reliability is improved, but loopback synchronization errors occur
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 later identify and prevent loopback synchronization cycles, thereby resolving the contradiction between maintaining high availability through replication and preventing synchronization errors.
Solution Approach 2:
The patent implements feedback by introducing a mechanism where the synchronization service monitors synchronization tags and timestamps to detect when data has already been synchronized to a particular database instance. This feedback loop enables the system to prevent re-synchronization of the same data, thus avoiding loopback errors while maintaining the reliability benefits of multi-region replication.
2Stability of the object's composition
If automatic synchronization is implemented between database instances, then data consistency is improved, but synchronization loops are created
Solution Approach 1:
The patent applies preliminary action by pre-marking synchronized data with synchronization tags and timestamps before the synchronization process completes. This allows the system to maintain automatic synchronization for data consistency while using these preliminary markers to detect and prevent synchronization loops.
Solution Approach 2:
The patent uses synchronization tags and timestamps as intermediary elements that mediate between the source and target database instances. These intermediaries carry information about the synchronization history, enabling the synchronization service to distinguish between legitimate data propagation and harmful synchronization loops, thus maintaining data consistency without creating loops.
3Difficulty of detecting and measuring
If synchronization tags and timestamps are added to track loopbacks, then loopback detection capability is improved, but device complexity increases
Solution Approach 1:
The patent applies universality by designing the synchronization tags and timestamps to serve multiple functions: they mark synchronized data, enable loopback detection, and provide ordering information for synchronization. This multi-functionality allows the system to improve loopback detection capability without proportionally increasing complexity, as the same fields serve multiple purposes in the synchronization mechanism.
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.