[
https://issues.apache.org/jira/browse/YUNIKORN-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342991#comment-17342991
]
Chaoran Yu commented on YUNIKORN-641:
-------------------------------------
[[email protected]] The second approach that you proposed (i.e. doing it on
the shim side in handleReleaseAppAllocationEvent) sounds cleaner to me. It
would be great if the work in this Jira can add to the application object the
info about the gang-originating pod. This would be useful for potentially
other cases too (e.g. For Spark, the driver pod brings the gang info and needs
to have events posted back to it).
> Add events for placeholder timeout to pod
> -----------------------------------------
>
> Key: YUNIKORN-641
> URL: https://issues.apache.org/jira/browse/YUNIKORN-641
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: core - scheduler, shim - kubernetes
> Reporter: Wilfred Spiegelenburg
> Assignee: Manikandan R
> Priority: Major
>
> If a placeholder times out we should communicate that fact with the pod that
> triggered the creation of the placeholders.
> An event should be added to the pod to show the timeout has occurred.
> Originally there could have been a request for 10 placeholders and only 5
> were used. The placeholder timeout events make it possible to track that on
> the original pod.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
