• Type: Bug
• Resolution: Unresolved
• Priority: Major
• Component/s: kubernetes-plugin
• Labels:

  None
• Environment:

  Jenkins ver. 2.176.3
  Kubernets-plugin: 1.19.3

1. 

   image-2019-10-28-11-48-19-811.png

   108 kB

   2019-10-28 10:48

[JENKINS-59959] The Concurrency Limit is not always respected.

Carl Dorbeus created issue - 2019-10-28 10:16

Carl Dorbeus made changes - 2019-10-28 10:18

Link

New: This issue relates to JENKINS-38260 [ JENKINS-38260 ]

Carl Dorbeus made changes - 2019-10-28 10:46

Description

Original: I create a lot of jobs 300 of them using jobdsl, lot of jobs in a short time. I have set the Kubernetes-plugin Concurrency Limit set to 20 Then Kubernetes plugin spins up a new node for almost every job. All but a few get in pending state due to resource limit in my Kubernetes cluster. Sometimes the concurrency Limit is respected, i see a lot of this in my jenkins log. but it should never get to to 184 running or pending. {code:java} INFO: Maximum number of concurrently running agent pods (20) reached for Kubernetes Cloud kubernetes, not provisioning: 184 running or pending in namespace jenkins with Kubernetes labels {jenkins=slave} {code}

New: I create a lot of jobs 300 of them using jobdsl. I have set the Kubernetes-plugin Concurrency Limit set to 20 Then Kubernetes plugin spins up a new node/pod for almost every job. All but a few get in pending state due to resource limit in my Kubernetes cluster. Sometimes the concurrency Limit is respected, i see a lot of this in my jenkins log. but it should never get to to 184 running or pending. {code:java} INFO: Maximum number of concurrently running agent pods (20) reached for Kubernetes Cloud kubernetes, not provisioning: 184 running or pending in namespace jenkins with Kubernetes labels {jenkins=slave} {code}

Carl Dorbeus made changes - 2019-10-28 10:48

Attachment

New: image-2019-10-28-11-48-19-811.png [ 49327 ]

Carl Dorbeus made changes - 2019-10-28 10:48

Description

Original: I create a lot of jobs 300 of them using jobdsl. I have set the Kubernetes-plugin Concurrency Limit set to 20 Then Kubernetes plugin spins up a new node/pod for almost every job. All but a few get in pending state due to resource limit in my Kubernetes cluster. Sometimes the concurrency Limit is respected, i see a lot of this in my jenkins log. but it should never get to to 184 running or pending. {code:java} INFO: Maximum number of concurrently running agent pods (20) reached for Kubernetes Cloud kubernetes, not provisioning: 184 running or pending in namespace jenkins with Kubernetes labels {jenkins=slave} {code}

New: I create a lot of jobs 300 of them using jobdsl. I have set the Kubernetes-plugin Concurrency Limit set to 20 Then Kubernetes plugin spins up a new node/pod for almost every job. All but a few get in pending state due to resource limit in my Kubernetes cluster, the pending pods is removed after a while and then recreated. Sometimes the concurrency Limit is respected, i see a lot of this in my jenkins log. but it should never get to to 184 running or pending. {code:java} INFO: Maximum number of concurrently running agent pods (20) reached for Kubernetes Cloud kubernetes, not provisioning: 184 running or pending in namespace jenkins with Kubernetes labels {jenkins=slave} {code}

Rene Schönlein made changes - 2020-07-10 06:21

Priority

Original: Minor [ 4 ]

New: Major [ 3 ]

David Schott made changes - 2020-08-27 21:23

Assignee

New: David Schott [ shott85 ]

David Schott made changes - 2020-08-28 14:49

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

David Schott made changes - 2020-08-28 14:49

Status

Original: In Progress [ 3 ]

New: In Review [ 10005 ]

David Schott made changes - 2020-09-01 14:36

Resolution		New: Fixed [ 1 ]
Status	Original: In Review [ 10005 ]	New: Fixed but Unreleased [ 10203 ]

Vincent Latombe made changes - 2020-09-03 13:19

Released As		New: kubernetes 1.27.1
Status	Original: Fixed but Unreleased [ 10203 ]	New: Resolved [ 5 ]

Load more newer history items