Cluster Node Synchronization Without Blocking Operations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In clustered node systems, concurrent cluster operations and node synchronization often lead to performance issues, as existing methods either block cluster-wide operations or reduce node availability, causing inefficiencies and delayed start-ups due to the need for all nodes to be synchronized before new operations can begin.
Innovation Solution
A method and system for synchronization and configuration distribution across a cluster that allows nodes to join or rejoin without blocking cluster operations, by recording current operations versions, removing inactive nodes, and synchronizing them upon rejoining, enabling continuous cluster operations and updates during the synchronization process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If node synchronization is performed before allowing new cluster operations, then configuration consistency is maintained, but cluster productivity and node availability are reduced
Solution Approach 1:
The system records the operations version before node removal and prepares synchronization data in advance. When the node returns, the pre-prepared synchronization data is quickly applied, avoiding the need to wait for full synchronization before allowing new operations to proceed.
Solution Approach 2:
The patent enables continuous cluster operations during node synchronization by allowing new operations to start without waiting for the returning node to complete synchronization. The system maintains operational continuity by decoupling the operation start condition from the node synchronization completion condition.
2Reliability
If cluster operations are blocked during node synchronization, then configuration consistency is ensured, but node availability and service performance deteriorate
Solution Approach 1:
The system performs preliminary actions by recording the operations version and preparing synchronization data before the node actually needs to synchronize. This allows the node to be quickly brought back into service without blocking cluster operations, as the synchronization data is already prepared.
Solution Approach 2:
The patent introduces an intermediary mechanism (operations version recording and synchronization data preparation) that mediates between the returning node and the cluster operations. This intermediary allows the node to synchronize in the background without blocking new operations, maintaining both consistency and availability.
3Reliability
If all nodes must be synchronized before new operations start, then configuration consistency is maintained, but time loss and operational delays increase
Solution Approach 1:
The system records operations versions and prepares synchronization data in advance, before the node actually returns to the cluster. This preliminary preparation eliminates the need to wait for full synchronization before starting new operations, significantly reducing operational delays.
Solution Approach 2:
The patent implements a dynamic approach where the system adapts its synchronization requirements based on the operational context. New operations can start dynamically without waiting for node synchronization, while still ensuring consistency through the recorded operations version mechanism.
Data Source
AI summary
A method and system for synchronization and distribution of configuration cross cluster without blocking are provided herein. The method includes: responsive to detecting a node in the group of nodes of a distributed system becoming inactive, recording current operations database version as a node version of the inactive node; initiating a removal of the inactive node from the group of nodes; maintaining the version of the operations database unchanged until the inactive node is removed; enabling a change of the database version once the removal of the inactive node is completed; sending a join request once the inactive node wishes to rejoin; obtaining a list of operation objects for synchronization of the rejoining node; and accepting the rejoining node to the group, only whenever the joining node is at a same state as the nodes group, otherwise, repeating the sending of the join request until the synchronization is completed.