Cluster Management System for Hypothetical Event Response Planning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

System administrators face challenges in determining how a computer cluster will react to hypothetical events, such as server node failures or changes in application policies, without modifying the cluster's configuration, making it difficult to test resilience or predict the impact of changes on deployed applications.

Innovation Solution

A cluster management system that generates a response plan for hypothetical events by analyzing the current cluster state and configuration, identifying necessary actions to achieve a target configuration that satisfies application policies, without executing these actions within the cluster.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system administrator modifies the cluster configuration to test responses to events, then the system can evaluate response plans, but the actual cluster state and running applications are affected

Engineering Contradiction:
Improveresponse plan evaluation accuracyVSAvoidimpact on running applications
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system creates a copy of the cluster state including server nodes, application configurations, and resource allocations. This copy is used for simulating hypothetical events and evaluating response plans, allowing administrators to test modifications without affecting the actual running cluster and its applications.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system introduces an intermediary simulation environment that acts as a mediator between the administrator's testing needs and the actual cluster. This intermediary layer allows response plan evaluation by processing hypothetical events in isolation, preventing direct impact on production applications while maintaining evaluation accuracy.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If the system generates detailed response plans for hypothetical events, then the system administrator gains insight into potential cluster behavior, but the system complexity increases

Engineering Contradiction:
Improveinformation about cluster responseVSAvoidsystem architecture
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by pre-generating response plans for various hypothetical events before they actually occur. This includes pre-calculating the impact of potential server node failures, application policy changes, and resource modifications, allowing administrators to review and understand potential cluster behaviors in advance without adding operational complexity during actual events.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system segments the complex response plan generation process into distinct modules: event simulation, state modification, policy evaluation, and plan generation. Each module handles a specific aspect of the analysis, making the overall system more manageable and maintainable while providing comprehensive information about cluster responses to hypothetical events.

Inventive Principle:
Principle #1Segmentation

3Productivity

If the system executes response plans in the actual cluster, then the cluster configuration is updated to reflect the response, but the original cluster state is lost

Engineering Contradiction:
Improveresponse plan implementationVSAvoidcluster configuration stability
Core Design Contradiction:
ProductivityVSStability of the object's composition

Solution Approach 1:

The system maintains a copy of the cluster state for executing and testing response plans. After evaluation, the original cluster configuration remains unchanged, allowing administrators to review the impact before applying any changes. This ensures cluster stability while still enabling response plan implementation when desired.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system implements preliminary anti-action by preventing automatic execution of response plans in the actual cluster. Instead, it presents the planned changes to administrators for review and approval, allowing them to counteract or modify any changes they deem inappropriate before they are applied to the production cluster, thus maintaining configuration stability.

Inventive Principle:
Principle #9Preliminary anti-action

Data Source

PatentUS8793344B2System and method for generating a response plan for a hypothetical event
Publication Date: 2014.07.29 ORACLE INT CORP
  • US8793344B2 patent drawing
  • US8793344B2 patent drawing
  • US8793344B2 patent drawing

AI summary

A cluster management system can facilitate determining a response to a hypothetical event by a computer cluster. During operation, the system can receive a request for a policy outcome from a user, such that the request can indicate a hypothetical event within a computer cluster. Next, the system determines a cluster state that includes state information from a plurality of server nodes in the cluster. The system then generates a response plan to the hypothetical event based on the cluster state, without executing the response plan in the cluster. The response plan indicates actions that are to be performed by server nodes in the cluster in response to the hypothetical event. The system then provides the response plan to the user.