[
https://issues.apache.org/jira/browse/YUNIKORN-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko resolved YUNIKORN-2323.
------------------------------------
Fix Version/s: 1.6.0
Resolution: Fixed
> Gang scheduling user experience issues
> --------------------------------------
>
> Key: YUNIKORN-2323
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2323
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Affects Versions: 1.4.0
> Reporter: Manikandan R
> Assignee: Manikandan R
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
>
> In case of any issues, users are finding it bit difficult to understand what
> is going on with the gang app.
> Issue 1:
> "driver pod is getting struck"
> At times, when driver pod is not able to run successfully for some reasons,
> users are getting the perspective that pod is getting struck and app is
> hanged, not moving further. Users are waiting for some time and don't
> understand the clear picture. How do we close the gap quickly and communicate
> accordingly through events?
> Issue 2:
> ResumeApplication is fired when all ph's are timed out. Do we need to inform
> the users about this event as they may not clue any about this significant
> change?
> Issue 3:
> When Gang app ph's are in progress (and allocated), when there is request for
> real asks and there is resource crunch, do we need to trigger auto scaling?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
