You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bugSomething that is supposed to be working; but isn'tcoreIssues that should be addressed in Ray CoretriageNeeds triage (eg: priority, bug/not-bug, and owning component)
I specify an actor which uses a STRICT_PACK placement group scheduling strategy with placement_group_capture_child_tasks=True. That actor spawns several tasks which have no resource requirements (num_cpus=0). I expect the tasks to be scheduled on the same node as the actor, as the strategy is STRICT_PACK. Instead, the tasks are running on arbitrary nodes. This only happens if the tasks have no resource requirements.
The text was updated successfully, but these errors were encountered:
Yard1
added
bug
Something that is supposed to be working; but isn't
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
core
Issues that should be addressed in Ray Core
labels
Dec 12, 2022
bugSomething that is supposed to be working; but isn'tcoreIssues that should be addressed in Ray CoretriageNeeds triage (eg: priority, bug/not-bug, and owning component)
What happened + What you expected to happen
I specify an actor which uses a
STRICT_PACK
placement group scheduling strategy withplacement_group_capture_child_tasks=True
. That actor spawns several tasks which have no resource requirements (num_cpus=0
). I expect the tasks to be scheduled on the same node as the actor, as the strategy isSTRICT_PACK
. Instead, the tasks are running on arbitrary nodes. This only happens if the tasks have no resource requirements.Versions / Dependencies
master (df13a1d)
Reproduction script
Run on a cluster with multiple nodes each with <= 8 CPUs (eg. https://console.anyscale-staging.com/o/anyscale-internal/workspaces/expwrk_j4rphgl1yttb36lhzw59svlf/ses_subxaevyczw11qxaylf3m9qa)
Issue Severity
High: It blocks me from completing my task.
The text was updated successfully, but these errors were encountered: