Heartbeat Mechanism Using Switching Node Intermediary

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In large-scale distributed database systems, the increasing number of nodes leads to a significant increase in heartbeat requests and responses, resulting in increased load and resource consumption, which affects system reliability and fault detection time.

Innovation Solution

A switching node records the moments when messages are received from each node and uses this information to determine if a second node is available, allowing it to send a heartbeat response directly to the first node, reducing the number of heartbeat requests and responses and optimizing the heartbeat path.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If the number of nodes in the distributed database system increases to handle larger scale data, then the system capacity and data storage capability are improved, but the quantity of heartbeat requests and responses increases significantly, leading to increased load and resource consumption

Engineering Contradiction:
Improvenumber of nodesVSAvoidresource consumption
Core Design Contradiction:
Quantity of substanceVSLoss of energy

Solution Approach 1:

The switching node acts as an intermediary between nodes in the distributed database system. It records the availability status of each node and intercepts heartbeat requests, providing heartbeat responses directly when nodes are available, thereby reducing the number of actual heartbeat exchanges between nodes and lowering resource consumption.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The switching node creates a copy of the node availability information in its local memory. Instead of nodes continuously exchanging heartbeat requests and responses, the switching node uses its copied availability status to generate and send heartbeat responses directly, eliminating redundant communication and reducing resource usage.

Inventive Principle:
Principle #26Copying

2Reliability

If traditional heartbeat mechanism is used where nodes directly exchange heartbeat requests and responses, then node availability can be detected, but the heartbeat path is long and fault detection time is increased

Engineering Contradiction:
Improvenode availability detectionVSAvoidfault detection time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The switching node serves as an intermediary that maintains local records of node availability. When a heartbeat request is received, the switching node can immediately check its local records and send a response without requiring the request to traverse the full path to the target node and back, thereby shortening the fault detection time while maintaining reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If each node processes all incoming heartbeat requests and sends responses, then complete node-to-node verification is achieved, but the load on each node increases significantly

Engineering Contradiction:
Improvenode verification completenessVSAvoidnode processing capacity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The switching node acts as an intermediary that assumes the burden of processing heartbeat requests. It records node availability status and handles the generation of heartbeat responses, thereby relieving individual nodes from the burden of processing every heartbeat request while maintaining complete verification of node availability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The functions of multiple nodes in processing heartbeat requests are merged into the switching node. Instead of each node independently processing and responding to heartbeat requests, the switching node consolidates this functionality, using its local availability records to generate responses for all nodes, thereby reducing the overall processing load on the distributed system.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11128718B2Method, apparatus, and system for implementing heartbeat mechanism
Publication Date: 2021.09.21 HUAWEI TECH CO LTD
  • US11128718B2 patent drawing
  • US11128718B2 patent drawing
  • US11128718B2 patent drawing

AI summary

The method, an apparatus and a system for implementing a heartbeat mechanism, so as to reduce a quantity of heartbeat responses sent by a node, and reduce unnecessary resource consumption in a distributed database system. The solution includes: obtaining, a heartbeat request sent by a first node to a second node; recording, a first moment, wherein the first moment is a moment that the heartbeat request is received; querying, according to the identity of the second node from cached information, a second moment, wherein the second moment is a moment that the switching node most recently, where the cached information stores a correspondence between a moment at which the switching node receives a message and an identity of the node; and if an absolute value of a difference between the first moment and the second moment is less than a threshold, sending a heartbeat response to the first node.