Distributed Database Switchover for Resource Imbalance Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In DbaaS cloud environments, primary database instances often consume more resources than secondary instances, leading to resource imbalance and performance degradation due to heavy contention, which conventional switchover mechanisms fail to address effectively.

Innovation Solution

A proactive switchover process evaluates resource metrics and performance metrics to identify a primary database instance candidate based on available resources, switching roles when average response time does not meet Quality of Service (QoS) requirements, balancing resources within the database cluster.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the primary database instance is configured with the same number of resources as secondary instances to avoid degradation during failover, then reliability is improved, but resource utilization efficiency deteriorates due to resource imbalance and heavy contention on the primary instance

Engineering Contradiction:
Improvecluster capacityVSAvoidresource utilization efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements dynamic resource allocation by allowing the primary database instance to have different resource configurations than secondary instances. The system dynamically adjusts resource distribution based on operational needs, enabling the primary instance to consume more resources during normal operation while maintaining the ability to failover to secondary instances with equal resources when needed, thus resolving the contradiction between reliability and resource utilization efficiency

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the resource configuration parameter from fixed equality to flexible differentiation. By allowing primary and secondary instances to have different resource allocations, the system optimizes resource utilization during normal operation while maintaining failover capability through configuration flexibility, thereby improving both productivity and reliability

Inventive Principle:
Principle #35Parameter changes

2Productivity

If the primary databaseinstance consumes more resources for query processing and insert/update operations, then productivity is improved, but resource imbalance causes performance degradation due to heavy contention

Engineering Contradiction:
Improvequery processing capabilityVSAvoidperformance stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the database cluster into primary and secondary instances with differentiated resource allocations. The primary instance is allocated additional resources for query processing and insert/update operations, while secondary instances maintain adequate resources for replication and failover. This segmentation allows each instance to be optimized for its specific function, improving overall productivity while maintaining performance stability through proper resource distribution

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by assigning different resource characteristics to different instances based on their roles. The primary instance receives higher resource allocation for processing-intensive operations, while secondary instances are configured for replication and failover readiness. This localized optimization ensures each instance has the resources it needs for its specific function, resolving the contradiction between productivity and performance stability

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12572400B2Database switchover in a distributed database system
Publication Date: 2026.03.10 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US12572400B2 patent drawing
  • US12572400B2 patent drawing
  • US12572400B2 patent drawing

AI summary

A proactive switchover process in a distributed database system evaluates available resources for a plurality of database instances based on database performance metrics of the database instances and resource metrics for physical hosts of the database instances. Periodic collection and storing of the metrics dataset provide for estimating a switching time length required for switching a primary database instance candidate with the current primary database instance. Further estimating based on historic values informs the proactive switchover determination.