Cloud Instance Node Management for High Availability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud computing solutions that ensure high availability of applications by using a primary and secondary instance node configuration result in resource wastage due to the secondary node occupying the same resources as the primary node, and in scenarios with two primary nodes, resource utilization is inefficient, leading to potential service failures under high pressure.

Innovation Solution

An instance node management method that dynamically adjusts the resource configuration of secondary instance nodes to a minimum required specification based on the primary node's running information, allowing the secondary node to replace the primary node in case of failure, thereby reducing resource occupancy and enhancing application hosting capacity and scalability on the cloud platform.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a secondary instance node occupies the same resource as a primary instance node to ensure high availability, then reliability is improved, but resource utilization deteriorates

Engineering Contradiction:
Improvehigh availabilityVSAvoidresource waste
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent implements dynamic resource allocation where the secondary instance node's resource configuration is adjusted based on its state. When the secondary node is in standby state, it occupies minimal resources. When failover occurs and the secondary node becomes the primary node, it dynamically acquires additional resources to match the primary node's full capacity. This dynamic adjustment resolves the contradiction by ensuring reliability through standby capability while minimizing resource waste during normal operation.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the resource configuration parameters of the secondary instance node based on its operational state. The resource allocation is not fixed but varies between two states: a minimal configuration during standby and a full configuration during active operation. This parameter change approach allows the system to maintain high availability guarantees while optimizing resource utilization by matching resource allocation to actual operational needs.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If two primary instance nodes are used to ensure high availability, then reliability is improved, but resource utilization rate cannot reach 50%

Engineering Contradiction:
Improvehigh availabilityVSAvoidresource utilization rate
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements a dynamic failover mechanism where one instance node serves as primary and the other as secondary standby. During normal operation, only one node actively handles requests while the other remains in standby with minimal resource consumption. When failover occurs, the roles dynamically switch. This dynamic approach ensures high availability through redundancy while achieving resource utilization rates above 50% since only one node needs full resource allocation at any given time, unlike the static two-primary-node approach where both nodes must maintain full capacity.

Inventive Principle:
Principle #15Dynamics

3Productivity

If resource utilization rate reaches 50% with two primary nodes, then productivity is improved, but when a single point is faulty, all pressure is concentrated on the other active primary instance node

Engineering Contradiction:
Improveresource utilization rateVSAvoidservice continuity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements a standby instance node that serves as a pre-prepared cushion or buffer before failover occurs. The standby node is maintained in a ready state with minimal resources allocated, acting as insurance against potential failures. When the primary node fails, this pre-prepared standby node can immediately take over, preventing service interruption. This beforehand cushioning approach ensures service continuity while maintaining reasonable resource utilization, as the cushion (standby node) only consumes significant resources when actually needed for failover.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentEP3253028B1Method for managing instance node and management device
Publication Date: 2020.09.02 HUAWEI TECH CO LTD
  • EP3253028B1 patent drawingFigure 1~2
  • EP3253028B1 patent drawingFigure 3~4
  • EP3253028B1 patent drawingFigure 5~6

AI summary

The present invention discloses an instance node management method, including: creating a primary instance node for an application hosted on the cloud platform, where the primary instance node is configured to run an instance of the application; determining, according to running start information of the primary instance node, a minimum resource configuration specification required by a secondary instance node of the application, where the secondary instance node of the application is configured to replace, when the primary instance node of the application is faulty, the primary instance node of the application to run the instance of the application; and creating the secondary instance node of the application according to the minimum resource configuration specification, where a resource configuration specification of the secondary instance node of the application is less than a resource configuration specification of the primary instance node of the application. On a basis of ensuring high availability of an application that is hosted on a cloud platform, the instance node management method provided by an embodiment of the present invention can reduce occupancy of a spare resource and increase an application hosting capability and scale on the cloud platform.