Proactive Node Health Prediction for Database Availability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Database services face challenges in anticipating and adequately preparing for various hardware and software failures, leading to potential downtime and reduced availability, as current methods often fall short in predicting node health and proactively handling failures.

Innovation Solution

A computer system monitors health indicators for multiple nodes in a database cluster, generates a health status based on historical data, and predicts the likelihood of node health within a specified time frame, proactively transferring data and preventing new data storage on nodes predicted to fail, thereby maintaining high availability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple replicas are deployed on different nodes to ensure availability during failures, then system reliability is improved, but device complexity and cost increase

Engineering Contradiction:
Improvedatabase availabilityVSAvoidcluster configuration
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by proactively transferring data from nodes predicted to fail before actual failure occurs. The database manager identifies nodes with predicted failures and initiates data migration to backup nodes in advance, ensuring continuous availability without waiting for actual node failure.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring health indicators of database nodes and using this information to update failure predictions. The health status monitoring provides real-time feedback that feeds into the predictive models, enabling dynamic adjustment of failure prevention strategies.

Inventive Principle:
Principle #23Feedback

2Loss of time

If proactive data transfer is performed on nodes predicted to fail, then downtime is reduced, but system response time and processing overhead increase

Engineering Contradiction:
ImprovedowntimeVSAvoiddata transfer speed
Core Design Contradiction:
Loss of timeVSSpeed

Solution Approach 1:

Data transfer operations are performed in advance on nodes predicted to fail, rather than waiting for actual failure. This preliminary action minimizes the impact on service continuity by ensuring data is already migrated to backup nodes before the failing node becomes unavailable.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system maintains continuous data migration operations during off-peak times or in background processes, ensuring that data transfer activities continue without interrupting normal database operations. This allows proactive data movement while maintaining service continuity.

Inventive Principle:
Principle #20Continuity of useful action

3Measurement precision

If health indicators are continuously monitored and analyzed, then prediction accuracy is improved, but energy consumption and processing resources increase

Engineering Contradiction:
Improvehealth prediction accuracyVSAvoidmonitoring resource consumption
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The system monitors only the most critical health indicators relevant to node reliability rather than all possible metrics. This selective monitoring approach provides sufficient prediction accuracy while minimizing resource consumption by focusing on key parameters such as hardware health, software stability, and operational metrics.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system dynamically adjusts the number and type of health indicators monitored based on the operational context, node importance, and prediction confidence levels. During normal operation, fewer indicators are monitored, while increased monitoring intensity is applied when anomalies are detected or during critical periods.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10891182B2Proactive failure handling in data processing systems
Publication Date: 2021.01.12 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10891182B2 patent drawing
  • US10891182B2 patent drawing
  • US10891182B2 patent drawing

AI summary

Embodiments are directed to predicting the health of a computer node using health report data and to proactively handling failures in computer network nodes. In an embodiment, a computer system monitors various health indicators for multiple nodes in a computer network. The computer system accesses stored health indicators that provide a health history for the computer network nodes. The computer system then generates a health status based on the monitored health indicators and the health history. The generated health status indicates the likelihood that the node will be healthy within a specified future time period. The computer system then leverages the generated health status to handle current or predicted failures. The computer system also presents the generated health status to a user or other entity.