[
https://issues.apache.org/jira/browse/YUNIKORN-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236123#comment-17236123
]
Wilfred Spiegelenburg commented on YUNIKORN-402:
------------------------------------------------
I think this issue does not exist anymore now that we have merged YUNIKORN-317.
There is just one place that tracks the asks and allocations. There are no
longer in flight allocations that need to be confirmed by the cache.
In the application we have
[RemoveAllocationAsk|https://github.com/apache/incubator-yunikorn-core/blob/master/pkg/scheduler/objects/application.go#L298],
[RemoveAllocation|https://github.com/apache/incubator-yunikorn-core/blob/master/pkg/scheduler/objects/application.go#L867]
and
[RemoveAllAllocations|https://github.com/apache/incubator-yunikorn-core/blob/master/pkg/scheduler/objects/application.go#L895]
to handle the removals discussed. All three functions have a check build in to
make sure that the wait state transition is triggered when appropriate.
Please check and comment if my check was correct.
> Make sure when there is no allocation in an app, the app state is "Waiting".
> ----------------------------------------------------------------------------
>
> Key: YUNIKORN-402
> URL: https://issues.apache.org/jira/browse/YUNIKORN-402
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Reporter: Kinga Marton
> Assignee: Kinga Marton
> Priority: Major
>
> If there is no allocation for an app, according to
> [http://yunikorn.apache.org/docs/next/design/scheduler_object_states] it's
> status should be waiting instead of running, as mentioned here:
> https://issues.apache.org/jira/browse/YUNIKORN-201?focusedCommentId=17186402&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17186402
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
