Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Timeouts on EBS volumes can occur due to various reasons, such as
network outages, and can often be recovered after some time.
Timeouts are handled by Linux by remounting the underlying filesystem as
readonly which leads to a bad customer experience.
While the I/O timeout can be specified for the nvme driver via the
kernel commandline or modprobe.d, udev rules are the preferred way of
setting per device timeouts. This is required as local NVMe volumes must have
a finite timeout.
Before Change:
After Change:
As you can see, the nvme driver was initialized with the default 30s timeout. The udev rule for the EBS volume has been applied successfully as well as the already present rule for local NVMe storage.