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

[core][oom] Use retriable lifo policy for dask 3x nightly test #32361

Merged
merged 2 commits into from
Feb 10, 2023
Merged

[core][oom] Use retriable lifo policy for dask 3x nightly test #32361

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
91bb17a
dask
clarng Feb 9, 2023
cbc9f7c
[core][oom] use retriable lifo policy for dask x3 nightly test
clarng Feb 9, 2023
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 release/nightly_tests/dask_on_ray/dask_on_ray_app_config.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,9 @@
base_image: {{ env["RAY_IMAGE_NIGHTLY_CPU"] | default("anyscale/ray:nightly-py37") }}
# We use retriable_lifo as the workload can crash due to multiple tasks from different
# callers running on the same node, we also observed raylet memory leak that would
# trigger the group-by-policy to fail the workload.
# https://github.com/ray-project/ray/issues/32195
env_vars: {"RAY_worker_killing_policy": "retriable_lifo"}
debian_packages: []

python:
Expand Down