Database Query Engine Version Upgrade via Copy Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed database systems face connection loss issues during query engine version changes due to compatibility issues between different versions of query engines, especially when cross-region replication is involved, leading to potential access to incorrect data versions or downtime.

Innovation Solution

Implement a technique where a database copy is created and managed to allow seamless version changes by transitioning query engines to read-only mode, installing new versions on a separate instance, and redirecting connections to ensure minimal downtime and compatibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If query engine version is changed in distributed database system, then new features and bug fixes are obtained, but connection loss and downtime occur due to compatibility issues between different versions

Engineering Contradiction:
Improvequery engine versionVSAvoidconnection continuity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

A copy of the database is created before the query engine version change. This preliminary action ensures that the original database state is preserved, allowing seamless switching back if needed and enabling the version upgrade to proceed without risking connection loss for clients.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mechanism (copy database instance) that mediates between the old and new query engine versions. Clients can be gradually migrated from the old version to the new version through this intermediary, avoiding direct compatibility conflicts between different engine versions.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If query engine version is changed, then system functionality is improved, but access to incorrect data versions or downtime occurs

Engineering Contradiction:
Improvesystem functionalityVSAvoiddowntime
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent creates a copy of the database instance with the new query engine version while the original instance continues to serve clients. This copying approach allows the new version to be tested and validated without affecting the operational system, eliminating downtime during version transitions.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The database copy is created and configured with the new query engine version before any clients are migrated. This preliminary preparation ensures that when clients switch to the new version, the system is already ready, avoiding downtime and ensuring continuous access to correct data versions.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If cross-region replication is involved in version changes, then distributed system resilience is maintained, but compatibility issues between different query engine versions arise

Engineering Contradiction:
Improvedistributed system resilienceVSAvoidversion compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the distributed database system into multiple instances with different query engine versions. Each region or instance can operate with its own version, allowing gradual migration and avoiding compatibility conflicts across the entire distributed system while maintaining resilience.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically manages multiple query engine versions across different regions or instances. Clients can be dynamically routed to appropriate instances based on their compatibility requirements, allowing the system to adapt to version changes without losing resilience or encountering compatibility issues.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS12038946B1Minimizing connection loss when changing database query engine versions
Publication Date: 2024.07.16 AMAZON TECH INC
  • US12038946B1 patent drawing
  • US12038946B1 patent drawing
  • US12038946B1 patent drawing

AI summary

Connection loss may be minimized for performing database query engine changes. A distributed database system may include different instances of the query engine that provide access to a database. When an event to change the version of the query engine is detected, a copy of the database may be created and a new instance of the query engine created. Read-only access to the database may be maintained using the different instances of the query engine while the new instance may be upgraded to the different version of the query engine. Upon successful installation of the different version of the query engine at the new instance, the new instance may be given read-write access to the database using the copy of the database and other database instances may be upgraded to the different version of the query engine.