Skip to content
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

[Core] Ignore stale ReportWorkerBacklogRequest #50280

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jjyao
Copy link
Collaborator

@jjyao jjyao commented Feb 6, 2025

Why are these changes needed?

Related issue number

For ReportWorkerBacklogRequest that's received after the core worker is marked as dead, we should ignore. Otherwise, we will have permanently leaked backlogs.

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@jjyao jjyao added the go add ONLY when ready to merge, run all tests label Feb 6, 2025
send_reply_callback(Status::OK(), nullptr, nullptr);
return;
}

local_task_manager_->ClearWorkerBacklog(worker_id);
Copy link

Choose a reason for hiding this comment

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

if worker_id is not in the worker_pool, should one ClearWorkerBacklog(worker_id) anyway to set backlog to empty?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants