Predicting Data Unavailability in Distributed Database Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data processing systems, particularly large distributed database systems, face challenges in predicting and preventing data unavailability and loss events proactively, leading to costly and time-consuming reactive approaches that often result in system downtime and data loss.

Innovation Solution

A predictive analytics system that continuously monitors and collects structured and unstructured data from distributed database systems, forming high-dimensional feature vectors to analyze and predict potential data unavailability and loss events using machine learning models, enabling proactive identification and prevention of issues before they occur.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If high redundancy and backup are engineered into large database systems, then data loss is minimized and system availability is improved, but system cost and complexity increase

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

Solution Approach 1:

The system performs preliminary actions by continuously monitoring current operating state data and comparing it against historical data to predict potential failures before they occur. This allows proactive intervention to prevent data loss and system downtime, reducing the need for excessive redundancy while maintaining reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by continuously collecting operating state data, analyzing it through machine learning models, and using the results to predict future failures. This feedback loop enables dynamic adjustment of maintenance strategies and resource allocation, optimizing system reliability without proportionally increasing complexity.

Inventive Principle:
Principle #23Feedback

2Ease of repair

If reactive support services are used to diagnose and fix problems, then problems are addressed when they occur, but system downtime and data loss occur before fixes are applied

Engineering Contradiction:
Improveproblem resolutionVSAvoidsystem availability
Core Design Contradiction:
Ease of repairVSReliability

Solution Approach 1:

The system performs preliminary diagnostics and predicts failures before they cause system downtime or data loss. By analyzing current operating state data against historical patterns, the system identifies potential problems early, allowing maintenance to be scheduled during non-critical periods rather than forcing reactive repairs during outages.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides beforehand cushioning by predicting failures and alerting operators in advance, creating a buffer period between problem detection and actual system failure. This allows time for preparation, scheduling maintenance during low-impact periods, and preventing catastrophic failures before they occur.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Reliability

If manufacturers and vendors proactively monitor and predict failures, then system reliability is improved, but the difficulty of accurate prediction and implementation complexity increase

Engineering Contradiction:
Improvepredictive capabilityVSAvoidprediction system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system achieves universality by using a unified machine learning framework that can predict multiple types of failures across different database systems and configurations. The same core prediction engine handles various failure modes by analyzing different operating state parameters, reducing the need for separate prediction systems for each failure type.

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

Solution Approach 2:

The system implements self-service by automatically collecting operating state data, training prediction models on historical data, and generating failure predictions without requiring extensive manual configuration or expert intervention. This automation reduces implementation complexity while maintaining high predictive accuracy.

Inventive Principle:
Principle #25Self-service

4Ease of operation

If reactive technical support is used to collect operating information and diagnose problems, then diagnosis is performed after problems occur, but time is lost and costs increase

Engineering Contradiction:
Improvediagnostic processVSAvoiddiagnosis time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary data collection and analysis continuously in the background, building historical operating state data and training prediction models before failures occur. When a potential failure is predicted, the diagnostic information is already prepared and available immediately, eliminating the time delay associated with post-failure data collection and analysis.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9489379B1Predicting data unavailability and data loss events in large database systems
Publication Date: 2016.11.08 EMC IP HLDG CO LLC
  • US9489379B1 patent drawing
  • US9489379B1 patent drawing
  • US9489379B1 patent drawing

AI summary

Data unavailability and data loss events in a large distributed database system are predicted by proactively and substantially continuously collecting information about appliance states and operations in the database system, forming feature vectors of prescribed key information features, and classifying said feature vectors as indicative of possible DU/DL events based upon their similarity and closeness to stored historical feature vectors known to be relevant to DU/DL events.