Observability Loop for Database Cluster Health Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Database systems face slower processing times due to the need to access both table data and metadata, often stored in separate databases, especially for operations like large table scans or multiple queries, which can be time-consuming and inefficient.

Innovation Solution

Implementing an observability loop that monitors cluster health and executes recommended actions to optimize performance, allowing for scalable management of transactional database clusters, thereby improving processing efficiency by prioritizing and executing the highest-ranked actions to enhance cluster health.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If table data and metadata are stored in separate databases, then data organization and management are improved, but processing time increases due to the need to access both databases

Engineering Contradiction:
Improvedata organizationVSAvoidprocessing time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent combines table data and metadata into a single database system, eliminating the need to access separate databases. This merging resolves the contradiction by maintaining the organizational benefits while removing the performance penalty of inter-database access, directly addressing the processing time issue described in the background.

Inventive Principle:
Principle #5Merging (Combining)

2Productivity

If operations like large table scans or multiple queries are executed, then data processing capability is improved, but execution time increases substantially

Engineering Contradiction:
Improvedata processing capabilityVSAvoidexecution time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by maintaining optimized data structures and metadata indexes that enable faster query execution. This allows large table scans and multiple queries to be executed more efficiently without substantially increasing execution time, resolving the contradiction between processing capability and execution time.

Inventive Principle:
Principle #10Preliminary action

3Quantity of substance

If cluster size increases to handle more data, then data storage capacity is improved, but system complexity and management difficulty increase

Engineering Contradiction:
Improvedata storage capacityVSAvoidcluster management complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The database system implements self-service capabilities through automated cluster management, including automatic metadata management, query optimization, and resource allocation. This allows the system to handle increased cluster sizes and data volumes without proportionally increasing management complexity, as the system self-adjusts and optimizes automatically.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12164490B2Observability loop
Publication Date: 2024.12.10 SNOWFLAKE INC
  • US12164490B2 patent drawing
  • US12164490B2 patent drawing
  • US12164490B2 patent drawing

AI summary

Techniques for managing cluster of devices are described. The clusters may refer to machines or instances of transactional database. A server may control cluster management. The server may operate an observability loop to manage the clusters. The observability loop may operate a plurality of observer phases in parallel, each observer phase monitoring a different parameter relating to the health of the cluster and generating a recommended action to improve the health of the cluster if an incident is present. The observability loop may rank the recommended actions from the different observer phases and may execute the highest ranked recommended action.