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] Promote _spill_on_unavailable in NodeAffinitySchedulingStrategy to public API #34283

Closed
jjyao opened this issue Apr 11, 2023 · 0 comments
Assignees
Labels
core Issues that should be addressed in Ray Core core-scheduler enhancement Request for new feature and/or capability P1 Issue that should be fixed within a few weeks

Comments

@jjyao
Copy link
Collaborator

jjyao commented Apr 11, 2023

Description

In #34224, we introduced private _spill_on_unavailable flag to NodeAffinitySchedulingStrateg to fix #34170.

We should promote this flag to a public API

Use case

No response

@jjyao jjyao added enhancement Request for new feature and/or capability triage Needs triage (eg: priority, bug/not-bug, and owning component) P1 Issue that should be fixed within a few weeks core Issues that should be addressed in Ray Core Ray-2.5 and removed triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Apr 11, 2023
@jjyao jjyao self-assigned this Apr 11, 2023
@rkooo567 rkooo567 added Ray-2.6 and removed Ray-2.5 labels Jun 2, 2023
@rkooo567 rkooo567 added Ray-2.7 and removed Ray-2.6 labels Jul 17, 2023
@scv119 scv119 removed the Ray-2.7 label Jul 19, 2023
@edoakes edoakes closed this as completed Feb 13, 2025
@exalate-issue-sync exalate-issue-sync bot reopened this Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Issues that should be addressed in Ray Core core-scheduler enhancement Request for new feature and/or capability P1 Issue that should be fixed within a few weeks
Projects
None yet
Development

No branches or pull requests

4 participants