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.

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

[Feature] Add E2E Test for Autoscaler Nested Remote Functions #2568

Open
2 tasks done
Tracked by #2173
mimiliaogo opened this issue Nov 25, 2024 · 0 comments · May be fixed by #2610
Open
2 tasks done
Tracked by #2173

[Feature] Add E2E Test for Autoscaler Nested Remote Functions #2568

mimiliaogo opened this issue Nov 25, 2024 · 0 comments · May be fixed by #2610
Assignees
Labels

Comments

@mimiliaogo
Copy link

mimiliaogo commented Nov 25, 2024

Search before asking

  • I had searched in the issues and found no similar feature requirement.

Description

Add an end-to-end test for ray-project/ray#48519.
Specifically, add a nested remote function test:

  1. Make sure the autoscaler won't kill a node with blocking workers (i.e, total_resources == available_resources but idle duration = 0). This can happen when the parent node is in a blocking state waiting for its child task on another node to finish.
  2. Autoscaler can downscale node when idle duration > idleTimeOut

Use case

No response

Related issues

ray-project/ray#48519

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!
@mimiliaogo mimiliaogo added enhancement New feature or request triage labels Nov 25, 2024
@mimiliaogo mimiliaogo changed the title [Feature] Add E2E Test for PR: https://github.com/ray-project/ray/pull/48519 [Feature] Add E2E Test for Autoscaler IdleTimeOut Dec 3, 2024
@mimiliaogo mimiliaogo changed the title [Feature] Add E2E Test for Autoscaler IdleTimeOut [Feature] Add E2E Test for Autoscaler Nested Remote Functions Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants