Decentralized Container Load Balancing via Gossip Protocol

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing container load balancing technologies require centralized administration and policies, leading to inefficiencies in resource utilization and increased costs due to the need for specialized systems to coordinate resource distribution among multiple hosts.

Innovation Solution

A decentralized container load balancing system where each host in a cluster communicates and determines the optimal movement of containers based on resource availability and tags, allowing peer-to-peer load balancing without a central authority, enabling self-defining, sharing, and adaptive resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If centralized administration and policies are used for container load balancing, then resource distribution coordination is achieved, but system complexity and costs increase due to specialized coordination systems

Engineering Contradiction:
Improveresource distribution coordinationVSAvoidspecialized coordination systems
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Each host in the container cluster autonomously determines its own resource constraints and initiates container movement decisions without requiring centralized coordination. The hosts self-manage load balancing by comparing their resource states and autonomously selecting suitable destinations for container relocation, eliminating the need for specialized centralized coordination systems.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

A gossip protocol is introduced as an intermediary communication mechanism that enables hosts to share resource state information and container movement decisions peer-to-peer. This intermediary allows distributed coordination without requiring a centralized authority, as each host can propagate its state and receive updates from others through the gossip mechanism, achieving reliable resource distribution coordination through decentralized communication.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If centralized load balancing systems are implemented, then container placement is coordinated, but resource utilization efficiency decreases due to information delays and centralized bottlenecks

Engineering Contradiction:
Improvecontainer placement coordinationVSAvoidresource utilization efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically adapts to changing resource conditions through continuous gossip protocol updates. When resource constraints change on any host, that host immediately propagates the updated state through the gossip mechanism, enabling rapid container relocation decisions without waiting for centralized system updates. This dynamic peer-to-peer information sharing ensures resource utilization efficiency is optimized in real-time based on current cluster conditions.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

Each host continuously monitors its own resource state and provides feedback to the cluster through the gossip protocol. When a host becomes resource-constrained or has available capacity, it broadcasts this information peer-to-peer, enabling other hosts to make informed container placement decisions. This distributed feedback mechanism ensures efficient resource utilization by allowing the system to rapidly respond to changing conditions without centralized bottlenecks.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If hosts independently determine container movements, then system flexibility and adaptability improve, but coordination overhead increases among peer hosts

Engineering Contradiction:
Improvedynamic resource allocationVSAvoidpeer-to-peer communication protocols
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The gossip protocol serves multiple functions simultaneously: it propagates resource state information, coordinates container movement decisions, and maintains cluster-wide awareness of available capacity. This universal communication mechanism handles diverse coordination needs through a single standardized protocol, reducing the complexity that would otherwise arise from implementing separate specialized protocols for each coordination function.

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

Solution Approach 2:

Each host independently determines its own resource constraints and autonomously selects destination hosts for container movements based on information received through the gossip protocol. The hosts self-service their own load balancing needs without requiring complex centralized scheduling or coordination logic, thereby achieving high adaptability while keeping the coordination protocol relatively simple and standardized.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250013506A1Container load balancing and availability
Publication Date: 2025.01.09 KYNDRYL INC
  • US20250013506A1 patent drawing
  • US20250013506A1 patent drawing
  • US20250013506A1 patent drawing

AI summary

A system includes a container cluster including plural hosts that communicate with one another via a network. Each of the plural hosts includes a computing node that includes an operating system and a container runtime configured to run containers. Each of the plural hosts stores a respective member list that defines capabilities of the plural hosts in the container cluster. Each of the plural hosts is configured to identify another one of the plural hosts for running a container based on comparing tags of the container to the capabilities of the plural hosts defined in the respective member list. Each respective one of the plural hosts is configured to perform the identifying the another one of the plural hosts for running the container in response to determining the respective one of the plural hosts is resource-constrained from running the container.