You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Peter Bacsko (Jira)" <ji...@apache.org> on 2022/03/29 08:39:00 UTC
[jira] [Updated] (YUNIKORN-1161) Pods not linked to placeholders are stuck in Running state
[ https://issues.apache.org/jira/browse/YUNIKORN-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Bacsko updated YUNIKORN-1161:
-----------------------------------
Description:
If we create pods where the nam of the task group does not match the {{task-group-name}} annotation, then the real pods will not transition to Running state when the placeholder pods expire.
For example, extend the sleep batch job like that:
{noformat}
apiVersion: batch/v1
kind: Job
metadata:
name: batch-sleep-job
spec:
completions: 5
parallelism: 5
template:
metadata:
labels:
app: sleep
applicationId: "batch-sleep-job"
queue: root.sandbox
annotations:
yunikorn.apache.org/task-group-name: sleep-group-0
yunikorn.apache.org/task-groups: |-
[{
"name": "sleep-group",
"minMember": 5,
"minResource": {
"cpu": "100m",
"memory": "2000M"
},
"nodeSelector": {},
"tolerations": []
}]
{noformat}
This will result in "batch-sleep-job-nnnnn" pods that are not transitioning to {{Running}} and they have to manually terminated.
was:
If we create pods where the nam of the task group does not match the {{task-group-name}} annotation, then the real pods will not transition to Running state when the placeholder pods expire.
For example, extend the sleep batch job like that:
{noformat}
apiVersion: batch/v1
kind: Job
metadata:
name: batch-sleep-job
spec:
completions: 5
parallelism: 5
template:
metadata:
labels:
app: sleep
applicationId: "batch-sleep-job"
queue: root.sandbox
annotations:
yunikorn.apache.org/task-group-name: sleep-group-0
yunikorn.apache.org/task-groups: |-
[{
"name": "sleep-group",
"minMember": 6,
"minResource": {
"cpu": "100m",
"memory": "2000M"
},
"nodeSelector": {},
"tolerations": []
}]
{noformat}
This will result in "batch-sleep-job-nnnnn" pods that are not transitioning to {{Running}} and they have to manually terminated.
> Pods not linked to placeholders are stuck in Running state
> ----------------------------------------------------------
>
> Key: YUNIKORN-1161
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1161
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: shim - kubernetes
> Reporter: Peter Bacsko
> Priority: Major
>
> If we create pods where the nam of the task group does not match the {{task-group-name}} annotation, then the real pods will not transition to Running state when the placeholder pods expire.
> For example, extend the sleep batch job like that:
> {noformat}
> apiVersion: batch/v1
> kind: Job
> metadata:
> name: batch-sleep-job
> spec:
> completions: 5
> parallelism: 5
> template:
> metadata:
> labels:
> app: sleep
> applicationId: "batch-sleep-job"
> queue: root.sandbox
> annotations:
> yunikorn.apache.org/task-group-name: sleep-group-0
> yunikorn.apache.org/task-groups: |-
> [{
> "name": "sleep-group",
> "minMember": 5,
> "minResource": {
> "cpu": "100m",
> "memory": "2000M"
> },
> "nodeSelector": {},
> "tolerations": []
> }]
> {noformat}
> This will result in "batch-sleep-job-nnnnn" pods that are not transitioning to {{Running}} and they have to manually terminated.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org