Standby Node Designation in Multi-Node Clusters
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-node computing clusters, the risk of cluster unavailability increases due to single points of failure when the master node and standby node fail simultaneously, and synchronizing the standby node can consume significant processing resources and introduce additional failures.
Innovation Solution
A method where the master node determines service loss and transaction log status, sending new transactions to the standby node if service is resumed before transaction and timeout thresholds are exceeded, and designates a new standby node if thresholds are met, balancing resource consumption and availability risks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the standby node is synchronized with the master node to enable failover, then the reliability of the cluster is improved, but the processing resources are consumed and additional failure points are introduced
Solution Approach 1:
The patent applies partial synchronization by only replicating transaction logs to the standby node when necessary (when service loss is detected), rather than continuously synchronizing all data. This reduces processing resource consumption while maintaining sufficient reliability for failover scenarios.
Solution Approach 2:
The system performs preliminary detection of service loss between master and standby nodes before initiating full synchronization. By detecting service loss early and only then activating the standby node, the system avoids unnecessary processing resource consumption while ensuring reliability when actually needed.
2Loss of time
If the standby node is kept in hot standby with full synchronization, then the failover time is reduced, but the processing resources and risk of additional failures increase
Solution Approach 1:
Instead of maintaining full hot standby synchronization continuously, the system uses partial synchronization activated only when service loss is detected. This reduces the standby node's exposure to failure risks and processing resource consumption while maintaining acceptable failover times through selective activation.
Solution Approach 2:
The system treats the standby node synchronization state as a temporary, on-demand resource rather than a permanent continuous state. By activating synchronization only when needed and allowing it to be discarded when not needed, the system reduces the risk of additional failures while maintaining acceptable failover performance.
3Reliability
If multiple standby nodes are designated to reduce single point of failure risk, then the reliability is improved, but the processing resources and system complexity increase
Solution Approach 1:
The system designates standby nodes in advance but keeps them in a low-resource state until service loss is detected. This preliminary designation reduces management complexity by pre-identifying candidates without requiring continuous active synchronization, thus improving reliability without proportionally increasing system complexity.
Data Source
AI summary
Examples include designation of a standby node. Some examples may include designation of a new node as a standby node when new transactions logged at a master node during a loss of service between a designated standby node and the master node exceeds a transaction threshold before the duration of the loss of service exceeds a timeout threshold.