Cluster Configuration Management via Shared Memory and Tree Structure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Complex and distributed storage systems face challenges in efficiently and reliably managing configuration parameters across cluster nodes, often requiring trade-offs between reliability and efficiency.

Innovation Solution

A method and system for managing configuration parameters in a cluster configuration, where changes to configuration parameters are received and stored in shared cluster memory, distributed to all nodes, and applied as a single view, utilizing a tree structure to organize and update configurations, allowing for concurrent updates and notifications across nodes without node restarts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If configuration parameters are managed in a distributed storage system with multiple cluster nodes, then the system can handle larger amounts of information and provide better scalability, but the complexity of managing configuration parameters across all nodes increases significantly

Engineering Contradiction:
Improveamount of information storedVSAvoidconfiguration management complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent introduces a configuration management service as an intermediary component that mediates between administrators and the distributed cluster nodes. This service maintains a centralized configuration database and automatically distributes configuration parameters to relevant nodes, eliminating the need for manual configuration management across each node and reducing overall system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The configuration management service performs multiple functions including storing configuration parameters, validating configurations, distributing updates to nodes, and monitoring node status. This multi-functional approach consolidates what would otherwise require separate mechanisms for each task, simplifying the overall configuration management architecture.

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

2Reliability

If configuration parameters are updated across all cluster nodes simultaneously, then a unified configuration view is maintained ensuring reliability, but the time required to apply updates and the system downtime increases

Engineering Contradiction:
Improveconfiguration consistencyVSAvoidupdate application time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements dynamic configuration update mechanisms where the configuration management service can push updates to nodes asynchronously and monitor acknowledgment status. Nodes can apply configurations at different times based on their readiness and load conditions, allowing the system to maintain configuration consistency ultimately while avoiding simultaneous updates that would cause downtime.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system incorporates feedback mechanisms where nodes report their status and configuration application progress back to the configuration management service. This feedback loop allows the service to track which nodes have successfully applied updates and to retry or alert on failures, ensuring eventual consistency without requiring all nodes to be updated simultaneously.

Inventive Principle:
Principle #23Feedback

3Reliability

If configuration changes require node restarts to take effect, then configuration reliability is ensured, but system availability and operational efficiency decrease

Engineering Contradiction:
Improveconfiguration application reliabilityVSAvoidsystem availability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The configuration management service performs preliminary validation and preparation of configuration parameters before distributing them to nodes. It checks syntax, validates against schemas, and prepares update packages in advance, so that when nodes receive and apply configurations, the process is smooth and reliable without requiring restarts. This preliminary action ensures configurations are correct before deployment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces the mechanical approach of forcing node restarts to apply configurations with a software-based hot-reload mechanism. Configuration parameters are designed to be dynamically loadable by running services, allowing configuration changes to be applied in-memory without interrupting service operations, thus maintaining system availability while ensuring reliable configuration application.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Measurement precision

If configuration parameters are distributed to each cluster node individually, then configuration precision and node-specific control are improved, but the overhead and complexity of configuration management increases

Engineering Contradiction:
Improveconfiguration parameter precisionVSAvoidconfiguration distribution complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments configuration parameters into hierarchical categories (global configurations, cluster-level configurations, node-specific configurations, and service-level configurations). This segmentation allows precise control at each level while the configuration management service handles the distribution automatically based on the segment type, reducing the complexity of manual distribution while maintaining precision.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11212175B2Configuration management for cloud storage system and method
Publication Date: 2021.12.28 EMC IP HLDG CO LLC
  • US11212175B2 patent drawing
  • US11212175B2 patent drawing
  • US11212175B2 patent drawing

AI summary

A method, computer program product, and computer system for receiving a change to a configuration parameter associated with a first cluster node in a cluster configuration. The configuration parameter may be stored in a shared cluster memory. The configuration parameter may be distributed from the shared cluster memory to the cluster configuration.