[
https://issues.apache.org/jira/browse/YUNIKORN-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17096550#comment-17096550
]
Adam Antal commented on YUNIKORN-42:
------------------------------------
Had a discussion with [~wwei] and [~wilfreds] today, and here are some notes.
First of all, the scope of this issue is huge, so I'll create subtasks to
handle it more easily. The first milestone should be to have an event cache in
core which only considers application and queue based events. Later we can
think about pushing these events to the shim side, adding
pod(AllocationAsk)/node based events as well and API to expose this information
to the user - even UI support.
What is also important to have this run in a separate goroutine (similar to
{{PartitionManager}}) and be independent of the scheduler. We don't want to
have performance degradation as a side-effect of better trackability of events.
> 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
> Assignee: Adam Antal
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
