Skip to content

fix: FUSE processing queue depth after failed request drain - #47

Open
eakman-datadog wants to merge 1 commit into
v2.4-ddfrom
ea/log-unprocessed-fuse-request-count
Open

fix: FUSE processing queue depth after failed request drain#47
eakman-datadog wants to merge 1 commit into
v2.4-ddfrom
ea/log-unprocessed-fuse-request-count

Conversation

@eakman-datadog

Copy link
Copy Markdown

When nydusd replaces a crashed daemon, it attempts to requeue in-flight FUSE requests using FUSE_NOTIFY_RESEND. On kernels that do not support this notification, the drain fails and requests left on the processing queue remain stuck, blocking the applications that issued them.

Log the number of requests remaining on the processing queue after a failed resend so affected nodes can be identified and drained.

Overview

Please briefly describe the changes your pull request makes.

Related Issues

Please link to the relevant issue. For example: Fix #123 or Related #456.

Change Details

Please describe your changes in detail:

Test Results

If you have any relevant screenshots or videos that can help illustrate your changes, please add them here.

Change Type

Please select the type of change your pull request relates to:

  • Bug Fix
  • Feature Addition
  • Documentation Update
  • Code Refactoring
  • Performance Improvement
  • Other (please describe)

Self-Checklist

Before submitting a pull request, please ensure you have completed the following:

  • I have run a code style check and addressed any warnings/errors.
  • I have added appropriate comments to my code (if applicable).
  • I have updated the documentation (if applicable).
  • I have written appropriate unit tests.

When nydusd replaces a crashed daemon, it attempts to requeue in-flight
FUSE requests using FUSE_NOTIFY_RESEND. On kernels that do not support
this notification, the drain fails and requests left on the processing
queue remain stuck, blocking the applications that issued them.

Log the number of requests remaining on the processing queue after a
failed resend so affected nodes can be identified and drained.
@eakman-datadog
eakman-datadog force-pushed the ea/log-unprocessed-fuse-request-count branch from 56d2e8d to 81e271c Compare July 31, 2026 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant