[
https://issues.apache.org/jira/browse/YUNIKORN-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112208#comment-17112208
]
Wilfred Spiegelenburg commented on YUNIKORN-99:
-----------------------------------------------
First part of the documentation which will need to be added when done:
*Application states*
* New: new app that is incomplete, from here the app transitions into the
accepted state when it is completed (i.e. add an ask)
* Accepted: the application is ready and part of the scheduling cycle. On
allocation of the first ask the app moves into a starting state.
* Starting: the app has exactly one running container/pod. The application
transitions to running after more allocations are added to the app or if no
more no pods are expected (timeout or just one cont/pod for the app)
* Running: the normal state for the application, Containers/pods can start and
stop and are scheduled when requested.
* Waiting: An app that has no pending asks or running containers/pod will be
Waiting for new asks to be added and then move back into Running
* Completed: The app has signalled it is done and not expected to return
* Killed: Removed by the shim at the request of an admin or user
* Rejected: The application is rejected when it was added to the scheduler.
This only happens when a shim tries to add an app, when it gets created in a
New state, and the scheduler rejects the creation
> Enhanced FIFO scheduling for batch workloads
> --------------------------------------------
>
> Key: YUNIKORN-99
> URL: https://issues.apache.org/jira/browse/YUNIKORN-99
> Project: Apache YuniKorn
> Issue Type: New Feature
> Components: core - scheduler
> Reporter: Weiwei Yang
> Assignee: Wilfred Spiegelenburg
> Priority: Major
> Labels: pull-request-available
>
> An enhanced version of FIFO scheduling for batch workloads
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
