[
https://issues.apache.org/jira/browse/YUNIKORN-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg closed YUNIKORN-299.
------------------------------------------
Fix Version/s: 0.10
Resolution: Fixed
closing as application ID reuse works within the limits we can support
> Application should be accounted under correct queue if the same app was
> submitted earlier under different queue.
> ----------------------------------------------------------------------------------------------------------------
>
> Key: YUNIKORN-299
> URL: https://issues.apache.org/jira/browse/YUNIKORN-299
> Project: Apache YuniKorn
> Issue Type: Task
> Components: core - scheduler
> Reporter: Ayub Pathan
> Priority: Major
> Fix For: 0.10
>
>
> Steps to repro:
> # Submit App-01 under namespace “development”
> # Which results in creation of “development” queue.
> # Now, once the App-01 is complete, delete the namespace.
> # Queue “development” is not cleaned up and /v1/queues return the old queue
> information.
> # Now submit App-01 again under different namespace - say “test01"
> What is the expected behavior in this case?
> # Yunikorn should schedule the app in “test-01” queue?
> # or should run the app under old “development” queue, which is no more
> existing in terms of namespace..
> To me, it looks like #1 is accurate and #2 is a bug as the namespace no more
> exists and its not expected to run under non-existing, un-accounted queue..
> This can be a common use case if user or code submits an app with same name
> under different namespaces.
>
> Currently, Yunikorn considers app name while generating appID, suggestion is
> to consider namespace as well while generating the appID along with app name.
> In that case, every app is uniquely identified!
>
> This Jira can be used to discuss and brainstorm different approaches on how
> to address this issue.
>
> [~cheersyang] [~wilfreds]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
