Role Management in Distributed Clusters via High Availability Agents

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed clusters, the dual master node scenario due to network instability and application performance degradation often requires restarting the entire application service cluster, leading to significant downtime and delayed management tasks.

Innovation Solution

Implementing high availability agents on master and replica nodes that utilize an in-memory data grid to automatically detect failures, switch roles, and prevent dual master scenarios by designating a replica node as a new master and demoting it back when the original master is restored, thus maintaining unique roles within the cluster.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the entire application service cluster is restarted to resolve dual master node scenarios, then the cluster stability is restored, but the downtime and service interruption increase significantly

Engineering Contradiction:
Improvecluster stabilityVSAvoiddowntime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by implementing a role resolution mechanism that proactively detects and resolves dual master node scenarios before they cause significant damage. The master node monitors for duplicate master roles and automatically initiates role correction by demoting conflicting master nodes to replica status, preventing the need for complete cluster restarts and minimizing service interruption time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements self-service through automated role management where the master node autonomously detects dual master scenarios and resolves them without external intervention. The high availability agent continuously monitors node roles and automatically demotes conflicting master nodes, enabling the cluster to self-correct role conflicts and maintain stability without requiring manual restarts or external management actions

Inventive Principle:
Principle #25Self-service

2Device complexity

If manual intervention is used to resolve dual master node scenarios, then the complexity of automation is reduced, but the management efficiency and response time decrease

Engineering Contradiction:
Improveautomation complexityVSAvoidmanagement efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The system implements self-service through automated role management where the master node autonomously detects dual master scenarios and resolves them without external intervention. The high availability agent continuously monitors node roles and automatically demotes conflicting master nodes, enabling the cluster to self-correct role conflicts and maintain stability without requiring manual restarts or external management actions

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system employs feedback mechanisms where the master node continuously monitors the cluster state for dual master node scenarios. When a conflict is detected, the system provides feedback by triggering automatic role resolution procedures, demoting the conflicting master node to replica status, and updating the cluster state. This closed-loop feedback ensures rapid detection and correction of role conflicts, maintaining high management efficiency through automated responses

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10922199B2Role management of compute nodes in distributed clusters
Publication Date: 2021.02.16 VMWARE INC
  • US10922199B2 patent drawing
  • US10922199B2 patent drawing
  • US10922199B2 patent drawing

AI summary

In one example, a distributed cluster may include compute nodes having a master node and a replica node, an in-memory data grid formed from memory associated with the compute nodes, a first high availability agent running on the replica node, and a second high availability agent running on the master node. The first high availability agent may determine a failure of the master node by accessing data in the in-memory data grid and designate a role of the replica node as a new master node to perform cluster management tasks of the master node. The second high availability agent may determine that the new master node is available in the distributed cluster by accessing the data in the in-memory data grid when the master node is restored after the failure and demote a role of the master node to a new replica node.