[
https://issues.apache.org/jira/browse/YUNIKORN-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17064592#comment-17064592
]
Tao Yang commented on YUNIKORN-42:
----------------------------------
Thanks [~wangda] for raising this. This is also necessary and important to us.
One question is that why not consider all information together in the design? I
can see the way to collect and publish events for Pods, high level information
on Apps/Queues/Partitions may need to be considered as a whole, the whole
activities of scheduling process contain more information and should be more
valuable than separate informations on different levels, can we take that into
account? Hope to hear your thoughts.
> Better to support POD events for YuniKorn to troubleshoot allocation failures
> -----------------------------------------------------------------------------
>
> Key: YUNIKORN-42
> URL: https://issues.apache.org/jira/browse/YUNIKORN-42
> Project: Apache YuniKorn
> Issue Type: Task
> Reporter: Wangda Tan
> Priority: Major
>
> Now it is tricky to do troubleshoot for pod allocation, we need better expose
> this information to POD description.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
