-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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][state] Efficient get/list actors with filters on some high-cardinality fields #34348
Conversation
Signed-off-by: rickyyx <[email protected]>
I am planning to do similar things for tasks + workers + objects, and plan to work on other issues before optimizing for other resources, which usually has a lower cardinality I believe (e.g. placement groups, runtime-envs)? cc @rkooo567 |
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.
We should probably remove show_dead_jobs option
cc @scv119 for the protobuf approval |
Here: #34415 |
…dinality fields ray-project#34348 Signed-off-by: rickyyx <[email protected]> This improves the state API for listing/getting actors: if filtering by id/state/job, filtering is pushed down to the source (GCS). Other state API resources will be implemented in a similar way (e.g. tasks/workers).
…dinality fields ray-project#34348 Signed-off-by: rickyyx <[email protected]> This improves the state API for listing/getting actors: if filtering by id/state/job, filtering is pushed down to the source (GCS). Other state API resources will be implemented in a similar way (e.g. tasks/workers). Signed-off-by: elliottower <[email protected]>
…dinality fields ray-project#34348 Signed-off-by: rickyyx <[email protected]> This improves the state API for listing/getting actors: if filtering by id/state/job, filtering is pushed down to the source (GCS). Other state API resources will be implemented in a similar way (e.g. tasks/workers). Signed-off-by: Jack He <[email protected]>
…m state api (ray-project#34433) Similar to ray-project#34348 This pushes down the below filters to GCS (source-side) filtering. actor_id task id task name job id
Why are these changes needed?
This improves the state API for listing/getting actors: if filtering by id/state/job, filtering is pushed down to the source (GCS).
Other state API resources will be implemented in a similar way (e.g. tasks/workers).
Related issue number
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.