Health Probe Chaining for Load Balancer Resource Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Health probing in large server collections is resource-intensive due to the need for frequent communication with multiple servers, which can lead to inefficiencies and increased resource usage.

Innovation Solution

Implementing health probe chaining where a single probe packet is sent through a chain of servers, with each server verifying its position and sending an acknowledgement (ACK) to the previous server, allowing the load balancer to determine the status of all servers with only two signals, reducing resource usage and enabling efficient failure detection and management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional health probing is used where the load balancer sends separate probes to each server, then reliable failure detection is achieved, but resource usage increases significantly

Engineering Contradiction:
Improvefailure detection reliabilityVSAvoidresource usage for health probing
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The health probing process is segmented into multiple chains, where each chain contains a sequence of servers. Instead of probing all servers individually from the load balancer, the servers are divided into groups (chains) that can be probed collectively. This segmentation reduces the total number of probe transmissions required while maintaining reliable failure detection through the chained acknowledgment mechanism.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Intermediate servers in the chain act as mediators that forward probe packets to subsequent servers and generate acknowledgments based on their own operational status. Each server in the chain serves as an intermediary that relays information about its status and the status of subsequent servers, reducing the communication burden on the load balancer while maintaining comprehensive monitoring.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If health probes are sent frequently to monitor server status, then failure detection speed improves, but resource consumption increases

Engineering Contradiction:
Improvefailure detection speedVSAvoidenergy consumed by health probing
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

Multiple health probe operations are merged into a single probe packet that traverses a chain of servers. Instead of sending separate probes to each server, one probe packet combines the monitoring function for multiple servers, reducing the frequency of transmissions while maintaining comprehensive coverage. The chained acknowledgment system ensures that failure detection speed is preserved despite reduced probe frequency.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If separate health probes are sent to each server, then comprehensive status monitoring is achieved, but system complexity increases

Engineering Contradiction:
Improvestatus monitoring completenessVSAvoidhealth probing system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The health probe packet and acknowledgment mechanism serve multiple functions simultaneously: they monitor server status, detect failures, and provide a structured method for servers to report their operational state. The universal probe packet format can be used across different server types and chain configurations, reducing the need for specialized monitoring mechanisms while maintaining comprehensive status monitoring.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS7991867B2Server checking using health probe chaining
Publication Date: 2011.08.02 CISCO TECHNOLOGY INC
  • US7991867B2 patent drawing
  • US7991867B2 patent drawing
  • US7991867B2 patent drawing

AI summary

A load balancer sends a probe packet to a first server in a list of servers. Each server in the list sends the probe successively down the list of servers and acknowledges the probe if the server is healthy. The final server in the list sends a signal to the load balancer to indicate that the chain of server probing has completed successfully. In this manner, the load balancer (or other device performing the checking) only needs to send a single probe rather than probe each server in the list separately. Embodiments include serial and recursive acknowledgments from the servers, sending a beacon message upon failure, and other features.