• Type: Bug
• Resolution: Fixed
• Priority: Critical
• Component/s: influxdb-plugin
• Labels:

  • influxdb
  • leak
  • threads
• Environment:

  influxdb-plugin: 3.0.0
  Jenkins version: 2.289

[JENKINS-65622] Thread leak after upgrade to 3.0.0

Alexandre Gaudreault created issue - 2021-05-12 17:21

Alexandre Gaudreault made changes - 2021-05-12 17:30

Description

Original: After upgrading influxDB from 2.5 to 3.0.0 we started to have a huge amount of thread leak causing our jenkins instance to fail. We had to revert and redeploy Jenkins, and I was not able to capture a thread dump. We used telegraf to have an influxDB listener v2.

New: After upgrading influxDB from 2.5 to 3.0.0 we started to have a huge amount of thread leak causing our jenkins instance to fail. We had to revert and redeploy Jenkins, and I was not able to capture a thread dump. I will update this ticket if/when I am able to have more information on the thread leak. It happened about ~6h after startup, so for us this means after about 15,000 jobs, all with post-deploy influxDb publisher. We used telegraf to have an influxDB listener v2.

Alexandre Gaudreault made changes - 2021-05-12 19:49

Description

Original: After upgrading influxDB from 2.5 to 3.0.0 we started to have a huge amount of thread leak causing our jenkins instance to fail. We had to revert and redeploy Jenkins, and I was not able to capture a thread dump. I will update this ticket if/when I am able to have more information on the thread leak. It happened about ~6h after startup, so for us this means after about 15,000 jobs, all with post-deploy influxDb publisher. We used telegraf to have an influxDB listener v2.

New: After upgrading influxDB from 2.5 to 3.0.0 we started to have a huge amount of thread leak causing our jenkins instance to fail. We had to revert and redeploy Jenkins, and I was not able to capture a thread dump. I will update this ticket if/when I am able to have more information on the thread leak. It happened about ~6h after startup, so for us this means after about 15,000 jobs, all with post-deploy influxDb publisher. We used telegraf to have an influxDB listener v2, and configured the plugin to use the v2 HTTP clien

Alexandre Gaudreault made changes - 2021-05-12 19:49

Description

Original: After upgrading influxDB from 2.5 to 3.0.0 we started to have a huge amount of thread leak causing our jenkins instance to fail. We had to revert and redeploy Jenkins, and I was not able to capture a thread dump. I will update this ticket if/when I am able to have more information on the thread leak. It happened about ~6h after startup, so for us this means after about 15,000 jobs, all with post-deploy influxDb publisher. We used telegraf to have an influxDB listener v2, and configured the plugin to use the v2 HTTP clien

New: After upgrading influxDB from 2.5 to 3.0.0 we started to have a huge amount of thread leak causing our jenkins instance to fail. We had to revert and redeploy Jenkins, and I was not able to capture a thread dump. I will update this ticket if/when I am able to have more information on the thread leak. It happened about ~6h after startup, so for us this means after about 15,000 jobs, all with post-deploy influxDb publisher. We used telegraf to have an influxDB listener v2, and configured the plugin to use the v2 HTTP client.

Jesse Jordan made changes - 2021-08-04 17:48

Link

New: This issue causes JENKINS-66017 [ JENKINS-66017 ]

Aleksi Simell made changes - 2021-08-06 06:19

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Fixed but Unreleased [ 10203 ]

Aleksi Simell made changes - 2021-08-06 11:59

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

Aleksi Simell made changes - 2021-12-03 08:47

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]