This is an automated email from the ASF dual-hosted git repository.
wilfreds pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/yunikorn-site.git
The following commit(s) were added to refs/heads/master by this push:
new 899aa4af13 [YUNIKORN-2111] Update core application states (#364)
899aa4af13 is described below
commit 899aa4af13488103d0adcefa22c972858c020c38
Author: Yu-Lin Chen <[email protected]>
AuthorDate: Thu Jan 25 16:05:39 2024 +1100
[YUNIKORN-2111] Update core application states (#364)
Moved scheduler_object_states.md from design folder to developer_guider
folder.
Updated links to the document and a new graph based on the latest states
for the application.
Closes: #364
Signed-off-by: Wilfred Spiegelenburg <[email protected]>
---
docs/assets/application-state.png | Bin 117964 -> 136449 bytes
docs/design/gang_scheduling.md | 2 +-
.../scheduler_object_states.md | 5 ++---
docs/user_guide/sorting_policies.md | 2 +-
.../current/user_guide/sorting_policies.md | 2 +-
sidebars.js | 2 +-
6 files changed, 6 insertions(+), 7 deletions(-)
diff --git a/docs/assets/application-state.png
b/docs/assets/application-state.png
index 6c7f27e092..2af46e96e1 100644
Binary files a/docs/assets/application-state.png and
b/docs/assets/application-state.png differ
diff --git a/docs/design/gang_scheduling.md b/docs/design/gang_scheduling.md
index 1a09f729bc..44560ef11b 100644
--- a/docs/design/gang_scheduling.md
+++ b/docs/design/gang_scheduling.md
@@ -181,7 +181,7 @@ The scheduler processes the AllocationAsk as follows:
## Application completion
Application completion has been a long standing issue.
Currently, applications do not transition to a _completed_ state when done.
-The current states for the application are [documented
here](./scheduler_object_states.md).
+The current states for the application are [documented
here](developer_guide/scheduler_object_states.md).
However, at this point in time an application will not reach the _completed_
state and will be stuck in _waiting_.
This provides a number of issues specifically around memory usage and cleanup
of queues in long running deployments.
diff --git a/docs/design/scheduler_object_states.md
b/docs/developer_guide/scheduler_object_states.md
similarity index 97%
rename from docs/design/scheduler_object_states.md
rename to docs/developer_guide/scheduler_object_states.md
index 306e2eb031..86cc135aea 100644
--- a/docs/design/scheduler_object_states.md
+++ b/docs/developer_guide/scheduler_object_states.md
@@ -60,11 +60,10 @@ This is a final state and after this state the application
cannot be tracked any
* Failing: An application marked for failing, what still has some allocations
or asks what needs to be cleaned up before entering into the Failed state.
The application can be Failing when the partition it belongs to is removed
or during gang scheduling, if the placeholder processing times out, and the
application has no real allocations yet.
* Failed: An application is considered failed when it was marked for failure
and all the pending requests and allocations were already removed.
-This is a final state. The application cannot change state after entering.
+From this state the application can only move to the Expired state.
* Rejected: The application was rejected when it was added to the scheduler.
This only happens when a resource manager tries to add a new application, when
it gets created in a New state, and the scheduler rejects the creation.
-Applications can be rejected due ACLs denying access to a queue the
application has specified, or a placement via placement rules has failed.
-This is a final state. The application cannot change state after entering.
+Applications can be rejected due ACLs denying access to a queue the
application has specified, or a placement via placement rules has failed. From
this state the application can only move to the Expired state.
The events that can trigger a state change:
* Reject: rejecting the application by the scheduler (source: core scheduler)
diff --git a/docs/user_guide/sorting_policies.md
b/docs/user_guide/sorting_policies.md
index f806f9ef1b..982877a138 100644
--- a/docs/user_guide/sorting_policies.md
+++ b/docs/user_guide/sorting_policies.md
@@ -92,7 +92,7 @@ Short description: limit of one (1) application in Starting
or Accepted state
Config value: `stateaware`
This sorting policy requires an understanding of the application states.
-Applications states are described in the [application
states](design/scheduler_object_states.md#application-state) documentation.
+Applications states are described in the [application
states](developer_guide/scheduler_object_states.md#application-state)
documentation.
Before sorting applications the following filters are applied to all
applications in the queue:
The first filter is based on the application state.
diff --git
a/i18n/zh-cn/docusaurus-plugin-content-docs/current/user_guide/sorting_policies.md
b/i18n/zh-cn/docusaurus-plugin-content-docs/current/user_guide/sorting_policies.md
index 49d64e9002..b08da46bf9 100644
---
a/i18n/zh-cn/docusaurus-plugin-content-docs/current/user_guide/sorting_policies.md
+++
b/i18n/zh-cn/docusaurus-plugin-content-docs/current/user_guide/sorting_policies.md
@@ -89,7 +89,7 @@ partitions:
配置值： `stateaware`
此排序策略需要了解应用程序状态。
-应用程序状态在[应用程序状态](design/scheduler_object_states.md#application-state)文档中进行了描述。
+应用程序状态在[应用程序状态](developer_guide/scheduler_object_states.md#application-state)文档中进行了描述。
在对所有排队的应用程序进行排序之前，将应用以下过滤器：
第一个过滤器基于应用程序状态。
diff --git a/sidebars.js b/sidebars.js
index 18eff82614..d0a7d2140f 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -74,6 +74,7 @@ module.exports = {
'developer_guide/deployment',
'developer_guide/openshift_development',
'developer_guide/translation',
+ 'developer_guide/scheduler_object_states',
{
type: 'category',
label: 'Designs',
@@ -93,7 +94,6 @@ module.exports = {
'design/priority_scheduling',
'design/resilience',
'design/state_aware_scheduling',
- 'design/scheduler_object_states',
'design/config_v2',
'design/scheduler_configuration',
]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
