Distributed Cluster Reconfiguration via Node Delegation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cloud-based computing environments, conventional cluster reconfiguration methods are serial and inefficient, causing downtime and delays, especially in mission-critical applications, as they rely on a single master node, leading to undesirable delays during node additions or removals.

Innovation Solution

Distributing reconfiguration functionality among multiple nodes, where the master node delegates tasks to slave nodes, allowing parallel processing of reconfiguration tasks, such as node joining or leaving, based on factors like physical proximity, hardware resources, and performance history, ensuring that all nodes share the same logical volume layout and state.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If cluster reconfiguration is driven by a single master node, then the reconfiguration process is simple to manage, but the reconfiguration time is long and causes downtime

Engineering Contradiction:
Improvereconfiguration process complexityVSAvoidreconfiguration time
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent segments the cluster reconfiguration task by dividing it into multiple sub-tasks that can be executed in parallel across different slave nodes. Instead of a single master node handling all reconfiguration operations sequentially, the system identifies independent reconfiguration operations and distributes them to multiple slave nodes, enabling concurrent execution and significantly reducing overall reconfiguration time while maintaining manageable complexity through structured task distribution

Inventive Principle:
Principle #1Segmentation

2Device complexity

If cluster reconfiguration is driven by a single master node, then the control structure is simple, but the productivity during reconfiguration is low

Engineering Contradiction:
Improvecontrol structure complexityVSAvoidreconfiguration throughput
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The control structure is segmented into a master node that coordinates and assigns tasks, and multiple slave nodes that execute specific reconfiguration operations independently. This segmentation enables parallel processing of reconfiguration tasks, dramatically increasing reconfiguration throughput while maintaining a relatively simple control structure where the master node manages task distribution and synchronization

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent merges the reconfiguration execution capabilities across multiple slave nodes while maintaining centralized coordination from the master node. By combining the processing power of multiple nodes for parallel reconfiguration operations, the system achieves high productivity without requiring complete decentralization, thus balancing control simplicity with execution efficiency

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8805978B1Distributed cluster reconfiguration
Publication Date: 2014.08.12 ARCTERA US LLC
  • US8805978B1 patent drawing
  • US8805978B1 patent drawing
  • US8805978B1 patent drawing

AI summary

A reconfiguration is distributed among multiple nodes of a cluster. Upon detecting an initiation of a reconfiguration of the cluster, reconfiguration functionality is delegated from the master node to one or more slave nodes in the cluster. Thus, multiple nodes perform reconfiguration functionality in parallel, such that one or more slave nodes perform delegated reconfiguration tasks that would conventionally be performed by the master node. The cluster reconfiguration can be in the form of one or more nodes joining or leaving the cluster. Data to facilitate the cluster reconfiguration can be transmitted from the master node to a slave node to which reconfiguration functionality is being delegated. Such data can include, for example, identifiers of nodes joining or leaving the cluster and/or information concerning the architecture and shared storage media of the cluster.