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.

Sign up for GitHub

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

Jump to bottom

Clarify behavior of placement_group_capture_child_tasks in docs #46885

Merged
merged 5 commits into from
Aug 5, 2024
Merged

Clarify behavior of placement_group_capture_child_tasks in docs #46885

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
6444343
clarify pg behavior in docs
amogkam Jul 30, 2024
5da1041
Update doc/source/ray-core/scheduling/placement-group.rst
amogkam Jul 30, 2024
eedd2fe
Merge branch 'master' into pg-docs-clarify
amogkam Jul 30, 2024
02178fc
Merge branch 'master' into pg-docs-clarify
jjyao Aug 2, 2024
9675a91
Apply suggestions from code review
jjyao Aug 5, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions doc/source/ray-core/scheduling/placement-group.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -577,6 +577,11 @@ child tasks and actors to the same placement group, specify ``PlacementGroupSche
:start-after: __child_capture_disable_pg_start__
:end-before: __child_capture_disable_pg_end__

.. warning::
The value of ``placement_group_capture_child_tasks`` for a given actor isn't inherited from its parent. If you're creating nested actors of depth greater than 1
and should all use the same placement group, you should explicitly set ``placement_group_capture_child_tasks`` explicitly set for each actor.


[Advanced] Named Placement Group
--------------------------------

Expand Down
Loading