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

Multiple "idle" entries on Build Executor Status for non-existant executors

    • Jenkins 2.208

      We have a jenkins environment where we have a single server with multiple executors (4). Sometimes the display has multiple idles, even though all executors are in use:

          [JENKINS-57304] Multiple "idle" entries on Build Executor Status for non-existant executors

          Oleg Nenashev added a comment -

          It is for flyweight executors, I believe (e.g. for Pipeline). They may be indicated as idle in Web UI for a while.

          Do they disappear automatically after some time?

          Oleg Nenashev added a comment - It is for flyweight executors, I believe (e.g. for Pipeline). They may be indicated as idle in Web UI for a while. Do they disappear automatically after some time?

          Patrick Rose added a comment -

          I've just checked again now - there's still the same number of extra idles. I can check again tomorrow morning?

          Patrick Rose added a comment - I've just checked again now - there's still the same number of extra idles. I can check again tomorrow morning?

          Oleg Nenashev added a comment -

          No, it should be about minutes to deprovision them.

          Which version of Jenkins have you been using before the upgrade?

          Oleg Nenashev added a comment - No, it should be about minutes to deprovision them. Which version of Jenkins have you been using before the upgrade?

          Patrick Rose added a comment -

          2.174. I think we have had this happen before as well, but I'm not 100%.

          Patrick Rose added a comment - 2.174. I think we have had this happen before as well, but I'm not 100%.

          Patrick Rose added a comment -

          It looks like they've gone now (and we're updated to 1.746). I don't know whether it was fixed by the upgrade or the fact that the system would have been rebooted.

          May as well close this unless you can think of a reason to keep it open?

          Patrick Rose added a comment - It looks like they've gone now (and we're updated to 1.746). I don't know whether it was fixed by the upgrade or the fact that the system would have been rebooted. May as well close this unless you can think of a reason to keep it open?

          Oleg Nenashev added a comment -

          Fine with me. OTOH I do not see any patch which would fix the problem in the recent releases

          Oleg Nenashev added a comment - Fine with me. OTOH I do not see any patch which would fix the problem in the recent releases

          Marc Benstein added a comment -

          I'm seeing this same behavior after updating to 2.176.1. They do not seem to be disappearing automatically.

          Marc Benstein added a comment - I'm seeing this same behavior after updating to 2.176.1. They do not seem to be disappearing automatically.

          Hi Team,

          We are also seeing the same behavior listing more number of executor and using Jenkins version 2.176.2 recently upgraded.

          Seeing same in chrome and firefox.

          Senthilkumar Palanisamy added a comment - Hi Team, We are also seeing the same behavior listing more number of executor and using Jenkins version 2.176.2 recently upgraded. Seeing same in chrome and firefox.

          Pavly Farag added a comment -

          Hi Team,

          We are also having the same bahavior listing lot of idle executors only for master whenever master executor is set to 0.

          and it keeps increasing with time.. for now it reached 112 lines, we are using Jenkins 2.189

          Pavly Farag added a comment - Hi Team, We are also having the same bahavior listing lot of idle executors only for master whenever master executor is set to 0. and it keeps increasing with time.. for now it reached 112 lines, we are using Jenkins 2.189

          Hi All,

          We are also seeing the same issue since the last 3-4 days. Current Jenkins version 2.176.2. 

          Any pointers on this issue ?

           

          Valencia Serrao added a comment - Hi All, We are also seeing the same issue since the last 3-4 days. Current Jenkins version 2.176.2.  Any pointers on this issue ?  

          Chris Bayliss added a comment - - edited

          I am seeing the same issue in Jenkins version 2.190.1 We are running one master and all our builds are pipeline builds. 

          Chris Bayliss added a comment - - edited I am seeing the same issue in Jenkins version 2.190.1 We are running one master and all our builds are pipeline builds. 

          Oleg Nenashev added a comment -

          Oleg Nenashev added a comment - https://github.com/jenkinsci/jenkins/pull/4329  likely fixes it

          Ramon Leon added a comment -

          Assigned to me to keep track of it and added the lts-candidate as the PR seems to fix a bunch of tickets.

          Ramon Leon added a comment - Assigned to me to keep track of it and added the lts-candidate as the PR seems to fix a bunch of tickets.

          Ian Williams added a comment -

          See also: JENKINS-60348

          Ian Williams added a comment - See also: JENKINS-60348

          Oleg Nenashev added a comment -

          Released in 2.208

          Oleg Nenashev added a comment - Released in 2.208

            mramonleon Ramon Leon
            drugcrazed Patrick Rose
            Votes:
            6 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: