Extended Two-Phase Commit Coordinator for Database Availability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern business software systems face challenges in maintaining uninterrupted availability due to unplanned and planned downtime, which can be costly and complex to manage, especially in high-availability hardware clusters, and existing mechanisms increase complexity and risk of failure.

Innovation Solution

A distributed database system utilizing an extended two-phase commit process with a commit coordinator that sends queries to cohorts and their mirrors, allowing for transaction execution up to a commitment point, and sending commit or rollback messages based on successful execution, while also managing redundancy and fail-over processes to minimize downtime and enhance availability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If high-availability hardware clusters are set up to ensure uninterrupted business software availability, then system availability is improved, but hardware cost and system complexity increase

Engineering Contradiction:
Improvesystem availabilityVSAvoidhardware cluster complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates virtual copies (mirrors) of database cohorts that can assume the role of failed cohorts. These mirrors are software-based replicas that maintain identical data and state, allowing seamless failover without requiring complex hardware redundancy. The mirror cohort mechanism provides availability through software copying rather than hardware duplication.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The commit coordinator serves multiple functions: it manages transaction commits, monitors cohort health, coordinates failovers, and handles recovery. This multi-functional approach consolidates what would traditionally require separate hardware components into a single coordinating entity, reducing hardware complexity while maintaining availability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If mechanisms are implemented to enable software maintenance without downtime, then system availability is improved, but system complexity and failure risk increase

Engineering Contradiction:
Improvesystem availabilityVSAvoidmaintenance mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by maintaining mirror cohorts that are pre-configured and ready to immediately assume workloads upon failover. During maintenance, the mirror is already synchronized and prepared, eliminating the need for complex runtime switching mechanisms and reducing failure risk during maintenance operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The commit coordinator acts as an intermediary that manages the transition between primary and mirror cohorts during maintenance. It coordinates the handoff process, ensuring data consistency and proper state transfer, thereby simplifying the maintenance mechanism while maintaining system availability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of time

If cohort mirrors are used with extended two-phase commit, then transaction execution time is reduced, but coordination complexity increases

Engineering Contradiction:
Improvetransaction execution timeVSAvoidcommit coordination complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent extracts the coordination logic from the individual cohorts and centralizes it in the commit coordinator. This extraction allows mirrors to process transactions independently without complex peer-to-peer coordination, reducing the time overhead while managing complexity centrally rather than distributing it across all nodes.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8880486B2Distributed database system utilizing an extended two-phase-commit process
Publication Date: 2014.11.04 SAP SE
  • US8880486B2 patent drawing
  • US8880486B2 patent drawing
  • US8880486B2 patent drawing

AI summary

A distributed database system is provided in which a commit coordinator ensures that transactions spanning multiple database instances are committed or rolled back consistently. The commit coordinator utilizes an extended two-phase-commit process. The extension of the two-phase-commit process enables, that if within the distributed database cohorts store redundant data for a productive operation, only one of the cohorts out of a redundancy group are required. By this, the distributed database is prepared to continue operation even during shutdown or failure of single cohorts. Related apparatus, systems, techniques and articles are also described.