Cascading Failover for Blade Server Workload Resource Matching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data center failover systems often rely on standby resources that may not be optimized for the workload, leading to inefficient resource utilization and potential quality-of-service issues due to mismatches between data processing resource requirements and available resources.
Innovation Solution
Implementing a cascading failover method where a system management server transfers workloads from a failing blade server to an initial replacement server, and then further to a subsequent replacement server with better-matched resources, ensuring optimal resource alignment with workload demands.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a standby blade server is used for failover, then service continuity is maintained, but resource optimization is compromised because the standby server may not have resources that match the workload requirements
Solution Approach 1:
The failover system dynamically selects replacement servers based on real-time workload analysis and resource matching, rather than using a static standby server. The system continuously monitors resource requirements and adjusts the selection of replacement servers to optimize the match between available resources and workload demands.
Solution Approach 2:
The system changes the selection criteria for replacement servers from a fixed standby approach to a dynamic parameter-based matching approach. It analyzes multiple parameters including CPU requirements, memory needs, storage capacity, and network bandwidth to select the most appropriate replacement server from the pool of available servers.
2Loss of time
If a single failover transfer is implemented, then service restoration is achieved quickly, but resource optimization is limited because the first replacement server may not be the best match for workload requirements
Solution Approach 1:
The system performs preliminary analysis of workload requirements and pre-identifies multiple candidate replacement servers with their resource characteristics before the failover occurs. This allows the system to make informed decisions about the optimal replacement server sequence, balancing speed of restoration with quality of resource matching.
Solution Approach 2:
The failover process is segmented into multiple stages: initial failover to a quickly available server to restore service immediately, followed by subsequent transfers to better-matched servers as they become available. This segmentation allows the system to prioritize service continuity while progressively optimizing resource alignment.
Data Source
AI summary
Cascading failover of blade servers in a data center implemented by transferring by a system management server a data processing workload from a failing blade server to an initial replacement blade server, with the data processing workload characterized by data processing resource requirements and the initial replacement blade server having data processing resources that do not match the data processing resource requirements; and transferring by the system management server the data processing workload from the initial replacement blade server to a subsequent replacement blade server, where the subsequent replacement blade server has data processing resources that better match the data processing resource requirements than do the data processing resources of the initial replacement blade server.