-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[Datasets] Fix spread resource prefix tasks with no CPU requested. #22017
[Datasets] Fix spread resource prefix tasks with no CPU requested. #22017
Conversation
resources={"foo": 100}, _system_config={"max_direct_call_object_size": 0} | ||
) | ||
cluster.add_node(resources={"bar:1": 100}) | ||
cluster.add_node(resources={"bar:2": 100}, num_cpus=0) |
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.
maybe add GPU as well?
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.
Doesn't matter for this test. This test is ensuring that a task with the spread resource prefix and with num_cpus=0
is able to be placed on a node with 0 CPUs advertised, so it's orthogonal to whether or not the node has any GPUs.
Note that this fixes the |
Datasets tests ok, ready to merge. |
…22017) When applying the `_spread_resouce_prefix` hack, don't make the CPU resource a required resource when `num_cpus=0` is requested.
When applying the
_spread_resouce_prefix
hack, don't make the CPU resource a required resource whennum_cpus=0
is requested.Related issue number
Closes #22003
Checks
scripts/format.sh
to lint the changes in this PR.