Cluster Node Configuration via Partial Snapshot Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cluster management systems face inefficiencies in node configuration and resource utilization during cluster maintenance, particularly in determining the optimal nodes for updating and joining clusters, which can lead to increased resource occupation and time expenditure.
Innovation Solution
The system evaluates configuration version information across nodes to determine the suitability of partial or full snapshot updates, allowing for dynamic determination of nodes to send update information, with partial snapshot updates being used from responsive nodes and full updates from nodes with sufficient gab messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Duration of action of stationary object
If traditional backup approaches utilize snapshots or checkpoints to allow Applications to continue writing to the primary file system, then application continuity is maintained, but the lifetime of the snapshot becomes quite long and resource occupation increases
Solution Approach 1:
The patent segments the backup process into multiple phases: active snapshot phase for data collection, and transfer phase for moving snapshot data to backup storage. This segmentation allows the snapshot to be closed promptly after data collection, reducing its lifetime and resource occupation while maintaining application continuity during the active phase.
Solution Approach 2:
The system performs preliminary actions by pre-allocating backup storage resources and preparing transfer mechanisms before the snapshot is closed. This allows the snapshot data to be transferred efficiently without extending the snapshot lifetime, as the transfer preparation occurs independently of the snapshot's active period.
2Reliability
If clustering software configures potential redundant switch over target nodes before starting primary application operations, then failover readiness is improved, but time expenditure for configuration increases
Solution Approach 1:
The patent implements dynamic configuration where target node readiness is assessed continuously rather than through static pre-configuration. The system monitors node availability and configuration status in real-time, allowing failover to proceed as soon as conditions are met, thus reducing configuration time while maintaining reliability.
Solution Approach 2:
The clustering software performs self-service by automatically detecting and configuring target nodes based on current system state without requiring extensive manual pre-configuration. The system autonomously evaluates node readiness and initiates failover procedures when appropriate conditions are detected, reducing both configuration time and administrative overhead.
3Stability of the object's composition
If a node joins a cluster with full snapshot information upload, then configuration consistency is ensured, but resource occupation and time expenditure increase
Solution Approach 1:
The patent applies partial action by transferring only the necessary portion of snapshot data from the source node to the joining node, rather than performing a complete full-upload. The system determines the minimal required data set needed for configuration consistency, reducing resource occupation and transfer time while maintaining stability.
Solution Approach 2:
The system changes the parameter of data transfer completeness from 100% (full upload) to a optimized partial transfer based on actual configuration needs. By analyzing which configuration elements are essential for the joining node's functionality, the system transfers only those specific parameters, reducing resource consumption while ensuring adequate consistency.
Data Source
AI summary
Systems and methods for cluster maintenance are presented. In one embodiment a cluster configuration method includes: maintaining configuration information associated with a first node and a second node, including cluster configuration version information; evaluating the first node as a potential configuration update node for the second node, including evaluating an indication of potential partial snapshot update availability based upon the configuration information associated with the first node and configuration information associated with the second node; performing an update type selection, including continued analysis of partial snapshot update availability; and performing an update for the second node in accordance with results of the update type selection. Evaluating the first node as a potential configuration update node can include comparing an available configuration version indication associated with the first node to the available cluster configuration version indication associated with the second node.