[
https://issues.apache.org/jira/browse/YUNIKORN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg resolved YUNIKORN-103.
--------------------------------------------
Fix Version/s: 0.10
Resolution: Fixed
This has been fixed as part of YUNIKORN-483.
Applications will now progress from running to waiting based on allocations and
asks. They will transition automatically into completed state if they have been
in waiting for 30sec. The completed apps will be cleaned up after 3days and
removed from the system.
If an application has pending pods it will be in a running state as per the
state diagrams
> Web UI shows the applications as Runnnig, even if they are in Pending state
> ---------------------------------------------------------------------------
>
> Key: YUNIKORN-103
> URL: https://issues.apache.org/jira/browse/YUNIKORN-103
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - cache, webapp
> Reporter: Kinga Marton
> Assignee: Kinga Marton
> Priority: Minor
> Fix For: 0.10
>
> Attachments: Screenshot 2020-04-20 at 14.27.50.png, Screenshot
> 2020-04-20 at 14.28.24.png
>
>
> When there are some applications what are unschedulable due to some reason
> (in my case it was a resource problem), in the Kubernetes dashboard I could
> see that the Pod was in pending state, but the Yunikorn api showed that the
> application is running.
> I think this mismatch can cause misunderstandings and it would be good to
> have the status of an application in synch with the pod status, or at least
> document the state machine of the applications.
> [~wwei] do we have such a documentation? If yes, please share it with me and
> the issue can be closed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
