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

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • Component/s: ec2-plugin
    • Environment:
      Jenkins Master OS: Centos 6.9
      Jenkins Slave: Windows 2008R2
      ec2-plugin version: 1.39
    • 1.45

      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

            Assignee:
            Raihaan Shouhell
            Reporter:
            Shubham Dhoka
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: