Virtual Machine Cluster Peer-to-Peer Management via Heartbeat

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In virtual machine clusters, the master node often becomes a bottleneck, leading to performance issues and prolonged fault recovery times due to insufficient capacity to manage a large number of slave nodes, and faulty master node re-election can cause resource contention and data damage.

Innovation Solution

Each virtual machine in the cluster maintains a virtual machine list and communicates with neighboring virtual machines via heartbeat messages to determine status, allowing for peer-to-peer management and eliminating the need for a master node, thereby improving fault tolerance and performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a master node is used to manage all slave hosts in the cluster, then centralized control and coordination are achieved, but the master host becomes a bottleneck when managing a large quantity of slave hosts, deteriorating overall cluster performance

Engineering Contradiction:
Improvecentralized controlVSAvoidcluster performance
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent divides the centralized management function into distributed peer-to-peer management among multiple virtual machines. Instead of one master node managing all slaves, multiple VMs cooperate to manage the cluster, with each VM capable of managing other VMs. This segmentation eliminates the single point of congestion and distributes the management load across the cluster.

Inventive Principle:
Principle #1Segmentation

2Reliability

If a master host is used for monitoring and management, then unified service provision is achieved, but when the master host is faulty, slave hosts must re-elect a new master host, consuming time and prolonging fault recovery

Engineering Contradiction:
Improveunified serviceVSAvoidfault recovery time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by having multiple virtual machines pre-configured with management capabilities before any failure occurs. When a failure is detected, another VM that is already prepared can immediately take over management functions without requiring a time-consuming re-election process. This eliminates the bottleneck and delays associated with master host re-election.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If a master host architecture is used, then a single system mapping is provided for users, but when slave hosts lose contact with the master host, they re-elect a master host, causing two independent cluster sub-regions to exist, leading to resource contention and data damage

Engineering Contradiction:
Improveunified service mappingVSAvoidresource contention and data damage
Core Design Contradiction:
Ease of operationVSObject-generated harmful factors

Solution Approach 1:

The patent implements a feedback mechanism where virtual machines continuously exchange status information and coordination messages with each other. When a VM detects that another VM is unavailable, it receives feedback from other VMs about the current management state and adjusts its behavior accordingly. This prevents split-brain scenarios where multiple independent management regions contend for resources, as VMs can coordinate their actions based on real-time feedback from the cluster state.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10728099B2Method for processing virtual machine cluster and computer system
Publication Date: 2020.07.28 HUAWEI TECH CO LTD
  • US10728099B2 patent drawing
  • US10728099B2 patent drawing
  • US10728099B2 patent drawing

AI summary

The present disclosure provides a method for managing a virtual machine cluster. The method includes: sending, by the first virtual machine, a first heartbeat message to at least two neighboring virtual machines in the N virtual machines, so that the at least two neighboring virtual machines detect the first heartbeat message, where a result of detecting the first heartbeat message is used to determine a status of the first virtual machine, and the first virtual machine establishes a neighbor relationship with the at least two neighboring virtual machines according to the information about the N virtual machines; and detecting, by the first virtual machine as a neighboring virtual machine of a second virtual machine in the at least two virtual machines, a second heartbeat message sent by the second virtual machine.