Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-52440

High CPU usage caused by WindowsProcess input copy threads in ec2-plugin

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • ec2-plugin
    • Jenkins Master OS: Centos 6.9
      Jenkins Slave: Windows 2008R2
      ec2-plugin version: 1.39
    • 1.45

    Description

      I am using the ec2-plugin on jenkins to autoscale windows slaves. When these slaves are created, the plugin starts the input-copy and output-copy threads(Class WindowsProcess). However, the input copy threads threads do not die even when the slave is terminated from the AWS console or by the plugin itself. The threads keep utilizing the Jenkins CPU and eventually stress it enough to cause Jenkins master to crash.

      These threads can be seen under <JENKINS_URL>/monitoring?part=threads

      Attachments

        Activity

          sdhoka Shubham Dhoka created issue -
          sdhoka Shubham Dhoka made changes -
          Field Original Value New Value
          Environment Jenkins Master OS: Centos 6.9
          Jenkins Slave: Windows 2008R2
          Jenkins Master OS: Centos 6.9
          Jenkins Slave: Windows 2008R2
          ec2-plugin version: 1.39
          sdhoka Shubham Dhoka made changes -
          Summary Class WindowsProcess threads do not die thereby shooting the Jenkins CPU over time High CPU usage caused by WindowsProcess input copy threads in ec2-plugin
          sdhoka Shubham Dhoka made changes -
          Description I am using the ec2-plugin on jenkins to autoscale windows slaves. When these slaves are created, the plugin starts the input-copy and output-copy threads(Class WindowsProcess). However, these threads do not die even when the slave is terminated from the AWS console or by the plugin itself. The threads keep utilizing the Jenkins CPU and eventually stress it enough to cause Jenkins master to crash.

          These threads can be seen under <JENKINS_URL>/monitoring?part=threads
          I am using the ec2-plugin on jenkins to autoscale windows slaves. When these slaves are created, the plugin starts the input-copy and output-copy threads(Class WindowsProcess). However, the input copy threads threads do not die even when the slave is terminated from the AWS console or by the plugin itself. The threads keep utilizing the Jenkins CPU and eventually stress it enough to cause Jenkins master to crash.

          These threads can be seen under <JENKINS_URL>/monitoring?part=threads
          raihaan Raihaan Shouhell made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          raihaan Raihaan Shouhell made changes -
          Status In Progress [ 3 ] In Review [ 10005 ]
          raihaan Raihaan Shouhell made changes -
          Assignee Francis Upton [ francisu ] Raihaan Shouhell [ raihaan ]
          raihaan Raihaan Shouhell made changes -
          Released As 1.45
          Resolution Fixed [ 1 ]
          Status In Review [ 10005 ] Resolved [ 5 ]

          People

            raihaan Raihaan Shouhell
            sdhoka Shubham Dhoka
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: