Compute Node Location Update in Distributed Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed computing environments, compute nodes may become temporarily unavailable and then re-enabled, leading to issues with maintaining accurate location information and re-establishing communications, as existing systems lack efficient mechanisms for updating node inventory with updated addresses after nodes are brought back online.

Innovation Solution

A controller node dynamically checks the availability status of compute nodes and updates their location information in a global node inventory by receiving and storing updated addresses from the data center once the nodes are re-started or re-enabled, ensuring rapid re-establishment of communications and temporarily blocking user operations until nodes are fully accessible.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If compute nodes are temporarily stopped and re-enabled in a distributed computing environment, then the nodes can be taken offline for maintenance or updates, but the location information in the global node inventory becomes outdated and communications cannot be re-established

Engineering Contradiction:
Improvenode availabilityVSAvoidlocation information accuracy
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system performs preliminary actions by blocking user operations on a compute node before the node is fully available, preventing operations on unavailable nodes. This preliminary blocking action avoids communication failures and ensures that only available nodes receive user operations, thereby maintaining information accuracy about node availability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the controller node continuously monitors the availability status of compute nodes and updates the global node inventory accordingly. When a compute node transitions from unavailable to available, the system receives feedback about this status change and updates the location information in the global node inventory to reflect the current state, ensuring information accuracy.

Inventive Principle:
Principle #23Feedback

2Reliability

If the system waits for compute nodes to be fully available before allowing user operations, then communication reliability is improved, but system productivity decreases due to temporary blocking of operations

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidsystem throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary availability checks and blocks user operations on compute nodes before they are fully available. This preliminary action prevents communication failures by ensuring that user operations are only directed to nodes that are currently available, thereby maintaining communication reliability while minimizing the impact on productivity through targeted rather than blanket blocking.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If the system continuously monitors compute node availability to maintain accurate inventory information, then information accuracy is improved, but system complexity increases due to additional monitoring mechanisms

Engineering Contradiction:
Improveinventory information accuracyVSAvoidmonitoring system complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system uses feedback from compute nodes about their availability status to update the global node inventory. When compute nodes transition between available and unavailable states, they provide feedback about their status, and the controller node updates the inventory accordingly. This feedback-based approach maintains information accuracy with relatively simple monitoring mechanisms, avoiding the need for complex continuous monitoring of all node parameters.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11153173B1Dynamically updating compute node location information in a distributed computing environment
Publication Date: 2021.10.19 JUNIPER NETWORKS INC
  • US11153173B1 patent drawing
  • US11153173B1 patent drawing
  • US11153173B1 patent drawing

AI summary

An example controller node may, responsive to receiving a resource request from a client device, deploy a compute node for execution on a particular data center selected from data centers within a distributed computing system, and store at least one address assigned to the compute node in a node inventory data store. After storing the at least one address, and responsive to determining that the compute node is not accessible using the at least one address the controller node may determine, based on information received from the particular data center, that the compute node is still available for execution on the particular data center, and receive, from the particular data center, at least one updated address assigned to the compute node. The controller node may then update the node inventory data store to store the at least one updated address that is assigned to the compute node.