This repository has been archived by the owner on May 25, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 264
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #706 from thandayuthapani/master
Docs for task-order within Job
- Loading branch information
Showing
2 changed files
with
23 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# Task Priority within Job | ||
|
||
## Introduction | ||
|
||
When a workload is presented to kube-batch in the form of jobs or tasks, | ||
kube-batch prioritizes those job/tasks, so job/task with high priority is | ||
handled first. In this doc, we will look into how Tasks within job are prioritized. | ||
|
||
## Implementation | ||
|
||
Task priority in kube-batch is done by using either of following data | ||
|
||
1. Task's Priority given in TaskSpec(i.e. PodSpec as defined in the YAML) | ||
2. Task's Creation time | ||
3. Task's UID | ||
|
||
![taskordering](../../doc/images/task_order.png) | ||
|
||
If priority plugin in kube-batch is loaded, then priority is decided using | ||
task's priority that will be provided in TaskSpec. | ||
Else it checks for creationTime of tasks. Depending on which task has been created first, | ||
that task will be given high priority. If creationTime is also same, | ||
then UID is compared and then priority is decided. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.