You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2022/04/07 01:40:00 UTC

[jira] [Commented] (YUNIKORN-700) [Umbrella] Provide app centric diagnosis info

    [ https://issues.apache.org/jira/browse/YUNIKORN-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518536#comment-17518536 ] 

Wilfred Spiegelenburg commented on YUNIKORN-700:
------------------------------------------------

moving out to 1.1 as it is too late in the cycle to start new work

> [Umbrella] Provide app centric diagnosis info
> ---------------------------------------------
>
>                 Key: YUNIKORN-700
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-700
>             Project: Apache YuniKorn
>          Issue Type: New Feature
>            Reporter: Weiwei Yang
>            Priority: Major
>
> When user submits apps to yunikorn, each app has a number of pods. Sometimes if the app wasn't able to run smoothly, users want to know what happened in the scheduler. So that they can get more understanding about
> # why my app is not making progress
> # why my app fails
> # why my app cannot get all pods allocated
> # why my app hangs
> we need some mechanism in yunikorn in order to expose this info to the users, essentially that provides app-centric diagnosis info.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org