-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
Render tasks that are not schedulable on the dashboard. #7034
Render tasks that are not schedulable on the dashboard. #7034
Conversation
…resoureces available (because other actors are occupying them) to the dashboard.
Can one of the admins verify this patch? |
python/ray/dashboard/client/src/pages/dashboard/logical-view/Actor.tsx
Outdated
Show resolved
Hide resolved
python/ray/dashboard/client/src/pages/dashboard/logical-view/Actor.tsx
Outdated
Show resolved
Hide resolved
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.
LGTM, can be merged if the tests pass. I tried it out locally too.
Test FAILed. |
Test PASSed. |
@rkooo567 There are some test failures, see e.g. https://travis-ci.com/ray-project/ray/jobs/283233241 |
Test FAILed. |
Test PASSed. |
@pcmoritz The new commit should fix the bug. I will let you know if it passes tests. |
Test PASSed. |
Test FAILed. |
Test FAILed. |
jenkins retest this please |
Test FAILed. |
Test FAILed. |
jenkins retest this please |
Test FAILed. |
jenkins retest this please |
Test PASSed. |
Test FAILed. |
jenkins retest this please |
1 similar comment
jenkins retest this please |
Test PASSed. |
Why are these changes needed?
Currently, the dashboard's logical view only renders infeasible tasks (Tasks that will never be able to satisfy its requirement). But we also want to show tasks that are currently not schedulable because there are no available resources. (E.g. There is one gpu available and it is taken by one actor. If you initiate the new actor, it is pending until the first actor is freed). It is not identified as
infeasibleTasks
. This PR addresses this issue. Look at the picture below for better understanding.Q&A
Ready tasks are remained in the queue for a long time only if there are no allocatable resources although dependencies are ready. That being said, we can represent
WaitUntilResourceAvailable
tasks by using ready tasks. This is the core assumption of this PR, so please comment if this assumption is wrong. I commented this workaround solution can be addressed more cleanly by creating a new taskState,WaitUntilResourceAvailable
.ActorCreationTask
?Currently, the logical view of dashboard only supports
ActorCreationTask
. Future PRs will address this problem.Related issue number
RS-726
Test Plan
test_metrics.py
Checks
scripts/format.sh
to lint the changes in this PR.