[
https://issues.apache.org/jira/browse/YUNIKORN-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko resolved YUNIKORN-2618.
------------------------------------
Fix Version/s: 1.6.0
Resolution: Fixed
> Streamline AsyncRMCallback UpdateAllocation
> -------------------------------------------
>
> Key: YUNIKORN-2618
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2618
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: shim - kubernetes
> Reporter: Wilfred Spiegelenburg
> Assignee: Yun Sun
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
>
> if task is not found, a nil is returned from {{context.getTask}} in for
> {{response.New}} processing we should just log that fact and proceed to the
> next alloc. Simplifies the flow as we never need to check for a. nil task. We
> should never have a pod in the cache that does not exist as a task on an
> application.
> We retrieve the application using the application ID from the response to
> never use the object. We only use the application ID to pass into an event.
> The context event handler then does the exact same lookup again to process
> the event on the app.
> We need to become much smarter in this area, double or triple lookups,
> generate async events that just change the state of the app or task or kick
> off another event.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
