-
Notifications
You must be signed in to change notification settings - Fork 819
[bugfix] fix vllm sleep&wake_up produces meaningless output #5143
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
Conversation
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.
Summary of Changes
Hello @hjh0119, 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 addresses a critical bug in the vLLM integration, specifically when operating in GRPO colocate mode with sleep functionality enabled. The bug caused abnormal outputs after sleep
and wake_up
cycles due to an un-reset prefix cache. The fix ensures data integrity by explicitly clearing the prefix cache before the engine goes to sleep, preventing erroneous generations in subsequent inference steps.
Highlights
- Bug Fix: Resolves an issue where the vLLM engine could produce incorrect outputs after
sleep
andwake_up
operations ifreset_prefix_cache
was not explicitly called. This specifically impacted GRPO colocate mode, leading to abnormal outputs from validation steps until the next training step. - Implementation: Introduces a call to
self.engine.engine.reset_prefix_cache()
immediately before thesleep()
operation within the_fast_infer
method ofgrpo_trainer.py
. This ensures the prefix cache is cleared before the engine goes to sleep, preventing data corruption upon waking.
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 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 or fill out our survey 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
-
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. ↩
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.
Code Review
This pull request addresses a bug where the vLLM engine could produce incorrect outputs after a sleep/wake-up cycle. The fix, which involves calling reset_prefix_cache
before the engine sleeps, is correct and well-targeted. My review includes a suggestion to add a comment to the new code to improve future maintainability by clarifying its interaction with other parts of the code. Overall, this is a good fix.
* fix vllm meaningless output * add comments
…pe#5143) * fix vllm meaningless output * add comments
PR type
PR information
vllm-project/vllm#17103
Fix a bug: When the vllm engine executes
sleep
+wake_up
without callingreset_prefix_cache
, it may produce incorrect outputs.Impact: In GRPO colocate mode, when validate is enabled, all outputs from the first step of validation until the next training step will be abnormal.
Solution: Call
reset_prefix_cache
before eachsleep
operation.A simple reproduction code:
Write the detail information belongs to this PR.
Experiment results
Paste your experiment result here(if needed).