Node Port Maintenance via Simulated Failure Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cluster networks face challenges in performing maintenance on nodes without disrupting transaction data processing, requiring costly and time-consuming coordination between I/O management and maintenance teams.

Innovation Solution

Implementing a network policy that simulates node failure by blocking periodic health check messages, allowing maintenance personnel to prepare nodes for maintenance without interrupting transaction data processing, and using a back-up node to ensure seamless data processing continuity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual load balancer updates and team coordination are implemented for node maintenance, then maintenance can be performed, but maintenance duration increases and resource efficiency decreases

Engineering Contradiction:
Improvemaintenance capabilityVSAvoidmaintenance duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables self-service automation where the maintenance management server autonomously coordinates with the load balancer server to update node configurations during maintenance. The load balancer automatically receives updated node lists and adjusts traffic routing without requiring manual intervention from I/O management personnel, allowing maintenance to proceed independently while maintaining service reliability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The maintenance management server proactively pushes updated node configuration information to the load balancer server before maintenance begins or as it progresses. This preliminary action ensures the load balancer is already prepared with the correct node list, eliminating delays that would occur from waiting for manual updates after maintenance starts.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If manual load balancer updates are performed during maintenance, then node configuration can be updated, but human capital resources are tied up and efficiency decreases

Engineering Contradiction:
Improvenode configuration accuracyVSAvoidresource efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The load balancer server automatically receives and processes node configuration updates from the maintenance management server through automated communication protocols. This eliminates the need for I/O management personnel to manually update the load balancer, freeing them to perform other value-added tasks while ensuring configuration accuracy is maintained through systematic automated updates.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The manual mechanical process of I/O management personnel updating load balancer configurations is replaced with an automated electronic communication system. The maintenance management server electronically transmits node lists and configuration data to the load balancer server, which automatically processes and applies these updates, substituting human manual operations with automated computational processes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If constant communication between I/O management and maintenance teams is maintained, then coordination is achieved, but maintenance period extends and coordination overhead increases

Engineering Contradiction:
Improvemaintenance coordinationVSAvoidcoordination complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The maintenance management server consolidates the coordination functions for both the maintenance team and I/O management team into a single automated system. It maintains a unified node configuration state that is automatically synchronized with the load balancer, eliminating the need for separate communication channels and coordination protocols between different teams, thereby reducing overall coordination complexity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system implements automated feedback mechanisms where the maintenance management server continuously monitors maintenance status and automatically updates the load balancer server accordingly. The load balancer server also provides feedback on its current node configuration state, creating a closed-loop system that maintains coordination without requiring constant human communication, thus reducing coordination overhead while maintaining reliability.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20260113241A1Configuration of node port for maintenance without load balancer coordination
Publication Date: 2026.04.23 VISA INTERNATIONAL SERVICE ASSOCIATION
  • US20260113241A1 patent drawing
  • US20260113241A1 patent drawing
  • US20260113241A1 patent drawing

AI summary

A computer implemented method providing a network policy configured to prevent transaction data processing from being interrupted during maintenance performed on nodes in a cluster network. The network policy reduces maintenance period times and the amount of personnel needed to perform node maintenance by simulating node failure. The simulated node failure prevents new transaction data from being sent the node that is undergoing maintenance.