Skip to content

Conversation

@Abatom
Copy link
Contributor

@Abatom Abatom commented Jun 24, 2025

Support automatic instance removal after crash for P2pNcclConnector

Abatom added 24 commits June 23, 2025 11:17
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
@github-actions
Copy link

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @Abatom, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the resilience and stability of the P2pNcclConnector by introducing mechanisms for automatic detection and removal of unresponsive or crashed instances. It achieves this through a combination of timestamp-based health checks in the proxy, robust NCCL communication timeouts, and a connection blacklisting strategy, ensuring smoother operation in distributed environments.

Highlights

  • Automatic Instance Cleanup: The disagg_prefill_proxy_xpyd.py now tracks prefill_instances and decode_instances with timestamps. It automatically removes instances from its registry if their last known 'ping' (registration) is older than DEFAULT_PING_SECONDS, effectively cleaning up crashed or unresponsive instances.
  • NCCL Communication Timeout & Abort: Implemented a _with_timeout wrapper for NCCL send and receive operations in p2p_nccl_engine.py. This wrapper uses a ThreadPoolExecutor to monitor operations and calls ncclCommAbort if an NCCL operation exceeds nccl_timeout_s, preventing indefinite hangs.
  • Connection Blacklisting: A new address_black_list is introduced in P2pNcclEngine to temporarily store addresses of failed connections. Subsequent connection attempts to blacklisted addresses are prevented for a defined period, reducing retries to unresponsive peers.
  • ZMQ Send Timeout: ZMQ sockets used for establishing NCCL connections (_get_connect) are now configured with a SNDTIMEO option, preventing ZMQ send calls from blocking indefinitely during connection setup.
  • NCCL Abort API Exposure: The pynccl_wrapper.py now exposes the ncclCommAbort function, allowing the P2pNcclEngine to programmatically terminate hung NCCL communicators.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@mergify mergify bot added the documentation Improvements or additions to documentation label Jun 24, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request introduces automatic instance removal after a crash for the P2pNcclConnector. It adds timeout mechanisms for NCCL operations, blacklisting of addresses after failures, and pinging to maintain connections. The changes aim to improve the robustness and reliability of distributed KV cache transfer.

Abatom added 2 commits June 24, 2025 15:04
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
@Abatom Abatom force-pushed the handle_crashed_instances branch from 4796e19 to 8bd4318 Compare June 24, 2025 12:01
Abatom added 2 commits June 24, 2025 20:13
Signed-off-by: Abatom <[email protected]>
Signed-off-by: Abatom <[email protected]>
@Abatom Abatom closed this Jun 25, 2025
@Abatom Abatom changed the title [WIP][V1][P/D]Support automatic instance removal after crash for P2pNcclConnector [V1][P/D]Support automatic instance removal after crash for P2pNcclConnector Jul 14, 2025
@Abatom Abatom deleted the handle_crashed_instances branch July 16, 2025 12:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant