-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
[NIXL] Terminate handshake listener thread in shutdown #26404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
NickLucche
merged 1 commit into
vllm-project:main
from
markmc:nixl-shutdown-handshake-listener-thread
Oct 22, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using
__del__for resource cleanup is an anti-pattern in Python because its execution is not guaranteed. It may not be called if the object is part of a reference cycle, or during interpreter shutdown, which can lead to resource leaks that are hard to debug. The explicitshutdown()calls, like the one you've added in the tests, are the correct and reliable way to handle cleanup.Furthermore,
__del__can be invoked by the garbage collector at any time and from any thread. This makes the thread-safety ofshutdown()critical, but the current implementation is not thread-safe. For example:self._recving_transferswhile another clears it, causing aRuntimeError.self._nixl_handshake_listener_tcould be set toNoneby one thread after another has checked it forNonebut before calling.join()on it, resulting in anAttributeError.I strongly recommend removing the
__del__method and relying solely on explicitshutdown()calls. Ifshutdown()might be called concurrently from other paths, it should be protected with athreading.Lock.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Calling
shutdown()from here is convenient for tests - it means resources are cleaned up even without explicit shutdown calls. Outside of tests, we should be callingshutdown()explicitlyAnother example of us doing this: