[
https://issues.apache.org/jira/browse/YUNIKORN-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342605#comment-17342605
]
Manikandan R commented on YUNIKORN-641:
---------------------------------------
Thanks [~wilfreds].
We can pass "first pod" info as part of {{*si.AddApplicationRequest}} to the
core and {{Application.timeoutPlaceholderProcessing()}} can make use of the
same to send events.
Otherwise, instead of passing "first pod" info and sending events from core, we
can persists "first pod" info only in shim side app object and make use of the
same in shim side {{application#handleReleaseAppAllocationEvent}} and
eventually send events through {{events.GetRecorder().Eventf(..)}}. In this
approach, we re-use the events and avoid adding additional load on
{{*si.AddApplicationRequest}}. Please share your thoughts and correct my
understanding.
> 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]
