Dynamic Error Recovery Based on Real-Time Workload

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing computer system recovery methods do not effectively adapt to changing system loads, which can impact performance and service levels when errors occur, as they do not consider the current workload level or its direction.

Innovation Solution

An apparatus and method that include a monitoring module to measure workload characteristics, an error detection module, a system workload analysis module to determine the workload level and its direction, and a system recovery module that selects and initiates error recovery actions based on the workload level, minimizing impact on performance characteristics, and adjusts error occurrence rate thresholds accordingly.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If error recovery actions are initiated without considering system workload, then system reliability is improved, but system performance deteriorates

Engineering Contradiction:
Improveerror recoveryVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements dynamic error recovery by continuously monitoring workload characteristics and adjusting recovery actions based on real-time system state. The system transitions from static, predetermined recovery procedures to dynamic, workload-adaptive recovery, selecting different recovery strategies depending on whether the system is under low, medium, or high workload conditions.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the parameters of error recovery actions based on workload levels. When workload is high, the system modifies recovery parameters to be less intrusive (e.g., deferring non-critical recovery actions, using lighter-weight diagnostics). When workload is low, more aggressive recovery actions are permitted, thus resolving the contradiction between maintaining reliability and preserving performance.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If comprehensive error recovery actions are taken, then system reliability is improved, but loss of time increases

Engineering Contradiction:
Improveerror mitigationVSAvoidrecovery time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies partial error recovery actions based on workload conditions. Instead of always executing complete, time-consuming recovery sequences, the system performs only the necessary subset of recovery actions appropriate for the current workload level. During high workload periods, partial recovery (e.g., logging only, deferring full diagnostics) reduces time loss while maintaining essential reliability.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system performs preliminary assessments of workload conditions before initiating error recovery actions. By evaluating current system state in advance, the system can prepare appropriate recovery strategies, avoiding time-consuming trial-and-error approaches and enabling faster, more targeted recovery responses.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If error recovery actions are taken during high workload, then system reliability is improved, but system performance deteriorates further

Engineering Contradiction:
Improveerror handlingVSAvoidservice level
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically adjusts error handling strategies based on real-time workload monitoring. During high workload periods, the system automatically selects recovery actions that minimize service disruption, such as queuing non-critical recovery tasks, using asynchronous processing, or deferring recovery until workload decreases, thus maintaining service levels while still addressing errors.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent applies different quality levels of error recovery to different system components based on their criticality and current workload. Not all errors receive the same level of immediate attention; critical errors during high workload may receive prioritized handling, while non-critical errors are deferred or handled with lighter-weight procedures, optimizing the balance between reliability and performance.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9552263B2System, apparatus, and method to dynamically change system recoveries based on system load
Publication Date: 2017.01.24 MAPLEBEAR INC
  • US9552263B2 patent drawing
  • US9552263B2 patent drawing
  • US9552263B2 patent drawing

AI summary

A method for dynamically changing system recovery actions based on system load. The method includes measuring a value of a workload characteristic of a computer system over a period of time, detecting an error in the computer system, determining a workload level of the computer system, and selecting a set of error recovery actions in response to the system workload analysis module determining the workload level of the computer system. A workload characteristic defines a type of work performed by the computer system. A workload level can be based on user defined parameters or a measurement of the value of one or more workload characteristics.