Proactive Failover Node Evaluation for Application Availability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing failover technologies fail to evaluate the ability of secondary nodes to adequately service applications before failing over, leading to increased downtime and data loss when they are unable to do so.

Innovation Solution

Proactively evaluating failover nodes by identifying criteria they must satisfy and determining their ability to service applications before a primary node failure, and taking corrective actions to ensure service continuity, such as configuring or prioritizing other nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing failover technologies attempt to failover to a secondary node after detecting primary node failure, then application availability is maintained, but application downtime increases and data loss occurs when the secondary node is unable to adequately service the application

Engineering Contradiction:
Improveapplication availabilityVSAvoidapplication downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system proactively evaluates failover nodes before actual failover events occur by checking resource availability, capacity, and suitability criteria. This preliminary assessment ensures that when failover is needed, the selected node is guaranteed to be capable of servicing the application, eliminating the waste of time from attempting failover to inadequate nodes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system continuously monitors and evaluates failover node status, using feedback from resource availability checks and capacity assessments to dynamically update failover priorities. This feedback mechanism ensures that the most suitable nodes are selected for failover, preventing downtime caused by inadequate node selection.

Inventive Principle:
Principle #23Feedback

2Ease of operation

If static user-defined failover lists are used, then configuration simplicity is maintained, but the system cannot adapt to changing node capabilities and resource availability

Engineering Contradiction:
Improveconfiguration simplicityVSAvoidnode capability adaptation
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system replaces static failover lists with dynamic evaluation that continuously assesses node resource availability, capacity, and suitability. Failover priorities are automatically adjusted based on current system state, allowing the system to adapt to changing conditions while maintaining ease of operation through automated management.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system automatically evaluates and selects appropriate failover nodes based on predefined criteria and current resource availability, eliminating the need for manual configuration updates. The system self-manages failover priority adjustments in response to changing node capabilities, maintaining operational simplicity while achieving adaptability.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8918673B1Systems and methods for proactively evaluating failover nodes prior to the occurrence of failover events
Publication Date: 2014.12.23 ARCTERA US LLC
  • US8918673B1 patent drawing
  • US8918673B1 patent drawing
  • US8918673B1 patent drawing

AI summary

A computer-implemented method for proactively evaluating failover nodes prior to the occurrence of failover events may include (1) identifying at least one primary node that services at least one application, (2) identifying at least one failover node designated to service the application if the primary node were to fail, (3) prior to detecting failure of the primary node, proactively evaluating the failover node's ability to service the application if the primary node were to fail, and then (4) in response to determining that the failover node would be unable to adequately service the application if the primary node were to fail, proactively performing at least one corrective action that would cause the application to be adequately serviced if the primary node were to fail. Various other methods, systems, and computer-readable media are also disclosed.