Distributed Management Nodes for Supercomputer Network Scalability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current supercomputer management systems face challenges with increased complexity, including high latency, CPU overload, and limited error correlation due to centralized management protocols, which lead to congestion and potential paralysis as the number of nodes and interconnections grow, hindering the achievement of exaflop performance.

Innovation Solution

A method involving the organization of compute nodes into groups with dedicated management nodes, each executing independent management modules, allowing asynchronous communication and out-of-band management to reduce data transmission and processing load, enabling scalable management up to exaflop levels.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If centralized management protocols are used to manage supercomputer networks, then management functions can be consolidated, but latency increases and CPU overload occurs as the number of nodes grows

Engineering Contradiction:
Improvemanagement system complexityVSAvoidmanagement latency
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent divides the centralized management system into distributed management nodes, each responsible for managing a specific subset of compute nodes and switches. This segmentation reduces the communication latency between management and data planes by localizing management functions closer to the network elements they control.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hierarchical dimension to the management architecture, with multiple levels of management nodes (e.g., domain-level and global-level managers). This dimensional expansion allows the system to handle large-scale networks by distributing management responsibilities across different hierarchical levels, reducing latency at each level.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Power

If the number of compute nodes and switches increases to achieve higher performance, then computation power increases, but network maintenance messages overwhelm the management node

Engineering Contradiction:
Improvesupercomputer performanceVSAvoidmessage processing capacity
Core Design Contradiction:
PowerVSProductivity

Solution Approach 1:

The management workload is segmented across multiple management nodes, each handling a portion of the total maintenance messages. This distribution prevents any single management node from becoming overwhelmed as the supercomputer scales to higher performance levels with more nodes and switches.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces intermediary management nodes that aggregate and filter maintenance messages before forwarding them to higher-level management. This intermediary layer reduces the total message volume that reaches the global management system, maintaining productivity as the system scales.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If centralized error management is implemented, then error data can be collected in a single database, but error correlation capabilities are limited

Engineering Contradiction:
Improveerror managementVSAvoiderror correlation capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

Error management is segmented across distributed management nodes, each maintaining local error databases for their respective domains. This segmentation enables better error correlation within each domain while the hierarchical structure allows aggregation of error data across domains, enhancing overall correlation capabilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent combines distributed error databases at multiple hierarchical levels, merging local error data with global error data. This combination enables comprehensive error correlation across the entire supercomputer network while maintaining the benefits of distributed data collection.

Inventive Principle:
Principle #5Merging (Combining)

4Ease of operation

If individual error requests are transmitted from a single central point, then centralized control is maintained, but data transmission becomes laborious and inefficient

Engineering Contradiction:
Improvecentralized controlVSAvoiddata transmission overhead
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The central error management function is segmented into distributed error collectors at multiple management nodes. Each collector handles error data locally, reducing the transmission overhead to the central point. Only aggregated or significant error data is transmitted upward in the hierarchy, minimizing energy consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Error data is preliminarily processed and aggregated at distributed management nodes before being transmitted to the central management system. This preliminary action filters out redundant data and performs initial analysis, reducing the volume and complexity of data that requires centralized processing.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10826779B2Method for managing a network of compute nodes
Publication Date: 2020.11.03 BULL SA
  • US10826779B2 patent drawing
  • US10826779B2 patent drawing

AI summary

A method of managing a network of calculation nodes interconnected by a plurality of interconnection devices, includes organizing the calculation nodes into groups of calculation nodes, for each group of calculation nodes, connecting the interconnection devices interconnecting the nodes of the group to a group management node, the management node being dedicated to the group of calculation nodes on each management node execution of an administration function by the implementation of independent management modules, each management module of a management node being able to communicate with the other management modules of the same management node.