Destination-Specific IO Timeout Control in Distributed Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems use a constant input-output (IO) timeout for all transactions regardless of destination, leading to inefficient management of IO transactions due to varying processing rates among different storage systems, which can result in premature termination of transactions and decreased likelihood of successful completion.

Innovation Solution

Implementing a dynamic timeout framework that adjusts IO timeouts based on the destination of the transaction, using a data structure to store destination-specific timeouts obtained through test requests, allowing tailored management of IO transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a constant IO timeout is used for all transactions, then the system is simple to manage, but the likelihood of successful transaction completion decreases due to varying processing rates among different storage systems

Engineering Contradiction:
Improvelikelihood of successful transaction completionVSAvoidtimeout management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies local quality by assigning different timeout values to different storage system destinations based on their individual performance characteristics. Instead of using a uniform timeout across all destinations, the system tailors timeout parameters to each specific storage system's processing rate and response time, thereby improving transaction success likelihood without excessive complexity

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements parameter changes by dynamically adjusting the timeout parameter based on the destination storage system's performance metrics. The system modifies the timeout value parameter according to observed processing rates and response times of different storage systems, allowing optimal transaction management adapted to each destination's characteristics

Inventive Principle:
Principle #35Parameter changes

2Productivity

If a constant IO timeout is used for all transactions, then the timeout management is straightforward, but premature termination of transactions occurs due to varying processing rates

Engineering Contradiction:
Improvetransaction completion rateVSAvoidpremature termination time loss
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system applies local quality by configuring destination-specific timeout values that match each storage system's actual processing capabilities. This prevents premature terminations caused by uniformly short timeouts while avoiding the time waste of excessively long timeouts, thereby improving transaction completion rates without significant time loss

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements feedback by monitoring the actual performance of storage systems and using this information to set appropriate timeout values. The system observes response times and processing rates, then adjusts timeout parameters accordingly, creating a feedback loop that prevents premature terminations while maintaining efficient time management

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20260003808A1System and method for managing input-output timeouts based on data location
Publication Date: 2026.01.01 DELL PROD LP
  • US20260003808A1 patent drawing
  • US20260003808A1 patent drawing
  • US20260003808A1 patent drawing

AI summary

Methods and system for managing data in a distributed system are disclosed. To manage data in the distributed system, a host system may initiate an input-output (IO) transaction based on an occurrence of an IO transaction event being identified. The IO transaction may include storage commands to manage the data stored in a destination and/or to store the data in the destination. The IO transaction may have a dynamic timeout that defines a duration of time to receive confirmation of the IO transaction being processed by the destination prior to performing remedial processes by the host system.