Automated Database Replication Upgrade Controller

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database replication systems face complexity and cost issues, especially when scaling horizontally or vertically, due to the need for manual intervention and significant processing costs during technology upgrades, and the difficulty in restarting replication from old transactions.

Innovation Solution

The method involves stopping an upgrade using a first incremental update strategy, identifying the earliest open transaction and the last committed log record, executing an adaptive apply strategy to ensure data consistency, and resuming the upgrade with a second incremental update strategy, thereby automating the database replication system upgrade and reducing manual intervention and costs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual intervention is used during technology upgrades, then data consistency can be ensured, but the complexity and cost of the upgrade process increases significantly

Engineering Contradiction:
Improvedata consistencyVSAvoidupgrade process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs automatic self-upgrade by identifying the earliest open transaction, switching to adaptive apply strategy, executing the upgrade process, and switching back automatically without human intervention. The upgrade controller autonomously manages the entire upgrade lifecycle including strategy selection and execution.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system dynamically changes the replication strategy parameter from incremental update strategy to adaptive apply strategy during the upgrade process, and then switches back after completion. This parameter switching enables the system to handle the upgrade state differently while maintaining data consistency.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If manual reload of replicated tables is performed during upgrade, then data consistency is maintained, but processing time and costs increase

Engineering Contradiction:
Improvedata consistencyVSAvoidupgrade time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system identifies the earliest open transaction before the upgrade begins and uses this information to resume replication from the correct position after upgrade. This preliminary identification prevents the need for complete table reloads and reduces upgrade time significantly.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The replication process continues uninterrupted during the upgrade by switching to adaptive apply strategy that can handle the upgrade state, then switching back to incremental update strategy. This continuous operation eliminates downtime and avoids complete reloads.

Inventive Principle:
Principle #20Continuity of useful action

3Reliability

If replication is restarted from earliest open transaction, then data consistency is ensured, but processing costs increase when transactions are old

Engineering Contradiction:
Improvedata consistencyVSAvoidprocessing cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The adaptive apply strategy acts as an intermediary mechanism during the upgrade process, allowing the system to apply changes without reprocessing old transactions. It bridges the gap between the upgrade state and the incremental update strategy, avoiding the need to reprocess historical data.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If upgrade is performed without automation, then control over data consistency is maintained, but labor costs and complexity increase

Engineering Contradiction:
Improvecontrol over data consistencyVSAvoidupgrade automation
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

The upgrade controller automatically manages the entire upgrade process including identifying transactions, switching strategies, executing upgrades, and resuming replication. This self-service automation maintains control over data consistency while eliminating manual labor and reducing complexity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11630814B2Automated online upgrade of database replication
Publication Date: 2023.04.18 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11630814B2 patent drawing
  • US11630814B2 patent drawing
  • US11630814B2 patent drawing

AI summary

In an approach to improve online database replication by automating the upgrading of a database replications system online. Additionally, embodiments of the present invention stop an upgrade using a first incremental update strategy on data of a source database, identify an earliest open transaction from a first database to a second database, and identify a last committed log record identifier. Further, embodiments of the present invention execute an adaptive apply strategy on transactions including the earliest open transaction until the last committed log record identifier is reached by the adaptive apply strategy, and resume, by upgrade controller, the upgrade with a second incremental update strategy.