Fault-Tolerant Parallel Database Node Instantiation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing computing systems, particularly web servers, often lack comprehensive fault tolerance mechanisms that can effectively handle failures across all types of computing systems, leading to potential service disruptions.

Innovation Solution

A fault-tolerant parallel database system is established with a control node cluster and a compute node cluster, each including active and spare nodes, which can assume specific functions, along with embedded health detectors to monitor and manage service health, enabling automatic node instantiation and command sending for restart or termination based on service status.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a fault tolerant parallel database system with control node cluster and compute node cluster is established, then system reliability is improved, but device complexity increases

Engineering Contradiction:
Improvesystem reliabilityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system is segmented into distinct control node cluster and compute node cluster, with each node having specific assumable functions. This segmentation allows for modular fault tolerance where failures in one cluster do not necessarily propagate to others, improving reliability while keeping each module's complexity manageable.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Spare nodes are pre-configured and ready to assume functions of failed active nodes. The system performs preliminary preparation by maintaining standby spare nodes that can immediately take over when failures occur, eliminating the need for complex real-time decision-making during failure events.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If embedded health detectors are used to monitor service health, then detection precision is improved, but device complexity increases

Engineering Contradiction:
Improvedetection precisionVSAvoiddevice complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

Embedded health detectors automatically monitor service health and provide status indications without requiring external intervention. The system serves itself by using the detectors to generate actionable health information that triggers automatic responses, improving detection precision while minimizing the complexity of external monitoring infrastructure.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The health detectors provide continuous feedback on service status, enabling the system to automatically determine when restart or termination actions are needed. This feedback mechanism improves detection precision by providing real-time health information while keeping the complexity manageable through automated response protocols.

Inventive Principle:
Principle #23Feedback

3Productivity

If automatic node instantiation and service management is implemented, then productivity is improved, but device complexity increases

Engineering Contradiction:
ImproveproductivityVSAvoiddevice complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system automatically instantiates spare nodes and manages service states without requiring manual intervention. When failures are detected, the system self-corrects by automatically promoting spare nodes to active status and managing service restarts or terminations, improving productivity while containing complexity through automation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system automatically changes operational parameters such as node status (active/spare), service states (running/terminated), and resource allocation based on detected failures. This automated parameter adjustment improves productivity by eliminating manual configuration steps while managing complexity through predefined transition rules.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8984328B2Fault tolerance in a parallel database system
Publication Date: 2015.03.17 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8984328B2 patent drawing
  • US8984328B2 patent drawing
  • US8984328B2 patent drawing

AI summary

Embodiments are directed to establishing a fault tolerant parallel database system and to detecting the health of parallel database services. In an embodiment, a computer system establishes a control node cluster that includes at least one active control node and at least one spare control node. Each node of the control node cluster includes specific functions assumable only by other control nodes. The computer system also establishes a compute node cluster that includes at least one active computing node, at least one spare computing node, at least one active storage node and at least one spare storage node. Each of the computing and storage nodes includes specific functions assumable only by other computing and storage nodes. The computer system detects a failure of an active node and instantiates a corresponding spare node that is configured to perform the functions of the failed active node.