Fail Over Cluster System Service Priority Recognition

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing failover cluster systems do not consider the quality of service when determining the order of priority for failover, leading to delayed service resumption for users who demand higher service levels.

Innovation Solution

A cluster system that includes a priority recognizing processing module to consult the priority of frames received from client computers, determining the order of failover based on demanded service levels, ensuring that users who require higher service levels have their service resumed first.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If fail over is executed without considering the quality of service, then the fail over process is simple and fast, but the service resumption for users who demand higher service levels is delayed

Engineering Contradiction:
Improveservice resumption priorityVSAvoidfail over control mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary action by pre-configuring quality of service parameters and service level agreements before failures occur. The fail over control mechanism retrieves pre-defined priority information associated with different service levels, enabling ordered fail over without complex real-time decision-making during the failure event itself.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the fail over control mechanism monitors the actual service levels being provided to users and adjusts the fail over order accordingly. Priority information is continuously updated based on user demands and service quality requirements, ensuring that higher priority services are restored first when failures occur.

Inventive Principle:
Principle #23Feedback

2Speed

If fail over priority is determined based on service level demands, then higher service levels are resumed quicker, but the system complexity increases due to priority recognition and ordering mechanisms

Engineering Contradiction:
Improveservice resumption speedVSAvoidpriority recognition processing
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system introduces an intermediary mechanism - the fail over control module - that acts as a mediator between the cluster nodes and the fail over process. This intermediary handles the complexity of priority recognition, frame analysis, and ordered fail over execution, shielding the individual nodes from the complexity while enabling speedier service resumption for high-priority users.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system changes parameters by dynamically adjusting the fail over priority based on quality of service requirements. Different service levels are assigned different priority parameters, and the fail over control mechanism modifies the fail over sequence according to these parameters, enabling faster resumption for high-priority services without requiring fundamental system redesign.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If the fail over computer takes over too much load without considering running state, then service continuity is maintained, but the response speed of the fail over computer is lowered

Engineering Contradiction:
Improveservice continuityVSAvoidfail over computer response speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The system implements dynamics by making the fail over process adaptive rather than static. The fail over control mechanism dynamically determines the fail over order based on the current running states of computers and the priority levels of services. This dynamic adjustment ensures that computers with better running states or higher capacity handle critical services first, maintaining service continuity while preserving response speed through intelligent load distribution.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS7480814B2Fail over cluster system and fail over method
Publication Date: 2009.01.20 GOOGLE LLC
  • US7480814B2 patent drawing
  • US7480814B2 patent drawing
  • US7480814B2 patent drawing

AI summary

A cluster system coupled to a client computer via a network has plural nodes which provide services to the client computer. A first node of the plural nodes has a priority recognizing processing module, which consults a priority of a frame received from the client computer. A second node of the plural nodes has a fail over processing module, which performs fail over on plural software resources managed by the first node according to an order of fail over priority that is based on the priority consulted by the priority recognizing processing module of the first node.