[ 
https://issues.apache.org/jira/browse/YUNIKORN-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Craig Condit resolved YUNIKORN-589.
-----------------------------------
     Fix Version/s: 1.4.0
    Target Version: 1.4.0
        Resolution: Delivered

Resolved in 1.4.0 as we no longer have multiple app management plugins.

> Multiple app IDs could be generated for the same app
> ----------------------------------------------------
>
>                 Key: YUNIKORN-589
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-589
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: shim - kubernetes
>    Affects Versions: 0.10
>            Reporter: Chaoran Yu
>            Priority: Minor
>             Fix For: 1.4.0
>
>         Attachments: Screen Shot 2021-03-21 at 9.11.04 AM.png
>
>
> When multiple app management plugins are enabled (e.g. general and spark 
> operator plugins), each plugin will generate its own app ID for the same app. 
> This alone may not be a problem, but when viewing app states in the UI, it 
> can get confusing, especially when two plugins have different opinions 
> regarding the current state of the same application. We probably need to 
> introduce a mechanism to optionally indicate whether a plugin is exclusive or 
> not. If yes, then a plugin will prevent other plugins from acting on the same 
> app. 
> In the attached screenshot, both app IDs are for the same Spark job, the 
> first generated by the Spark operator plugin, the second by the general 
> plugin. The true state is that the app has completed, as indicated by the 
> operator. But the general plugin has no idea, as expected. In this case, we 
> should just show the first row. 
> Maybe this is mostly just a UI issue. But in the k8s shim, we also need a way 
> to tell that they are the same thing.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to