Storage Error Event Classification and Threshold Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing storage systems face challenges in efficiently managing error events during input/output (I/O) requests, particularly in identifying and mitigating component failures within storage area networks (SANs) to ensure continuous operation.
Innovation Solution
A method and system that classify error events by severity, set threshold values for event frequencies, and automatically restrict component usage if thresholds are violated, routing I/O requests through alternate paths when available, and logging failures when no alternate paths exist.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If error events are monitored and components are restricted when thresholds are violated, then system reliability is improved, but device complexity increases due to the need for event classification, threshold management, and alternate path routing
Solution Approach 1:
The system segments error events into different severity levels (fatal, major, minor) and applies different threshold values to different component types. This segmentation allows the complexity management system to handle errors in a structured, modular way, improving reliability without overwhelming complexity.
Solution Approach 2:
The system performs preliminary actions by pre-defining severity classifications and threshold values for different component types before errors occur. When errors are detected, the pre-established rules are applied automatically, reducing the complexity of real-time decision-making while maintaining high reliability.
2Productivity
If automatic component restriction is implemented when error thresholds are violated, then productivity is maintained by using alternate paths, but loss of time increases due to event monitoring, classification, and threshold comparison operations
Solution Approach 1:
The system performs preliminary classification of events into severity levels and pre-sets threshold values for different component types. This preliminary organization allows rapid comparison and decision-making when errors occur, maintaining productivity while minimizing the time lost to error handling operations.
Solution Approach 2:
The system continuously monitors error events and provides feedback by comparing actual error frequencies against pre-established thresholds. This feedback mechanism enables automatic component restriction and alternate path selection, maintaining productivity through rapid response while the structured feedback loop minimizes processing delays.
3Reliability
If comprehensive error event classification and threshold monitoring are implemented across all components, then reliability is improved, but ease of operation deteriorates due to the complexity of managing classifications and thresholds
Solution Approach 1:
The system segments components into standard types (storage devices, adapters, switches) with pre-defined threshold values for each type. This segmentation simplifies operation by providing a consistent, standardized approach to error management across diverse components, maintaining reliability while improving ease of operation.
Solution Approach 2:
The system changes parameters by establishing fixed severity levels (fatal, major, minor) and corresponding threshold values for different component types. These parameter changes create a standardized error management framework that improves reliability while making the system easier to operate through consistent, predictable error handling rules.
Data Source
AI summary
Method and system for managing error related events while a system is processing input/output (“I/O”) requests for accessing storage space is provided. Various components are involved in processing the I/O requests. Some of these components may also have sub-components. Events related to the various components are classified with respect to their severity levels. Threshold values for a frequency of these events is set and stored in a data structure at a memory location. When an event occurs, the severity level and the threshold value for the event are determined from the data structure. The actual frequency is then compared to the stored threshold value. If the threshold value is violated and there is an alternate path to route the I/O request, then the affected component is restricted and the alternate path is used to route the I/O request.