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

Pairs of throttled node labels no longer seem to work starting from version 1.536

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • Windows 7 x64 master and slaves running Java7

      我们使用此功能只允许使用 cuda 设备的有限数量的作业(请参阅配置截图)。从 1.536 版开始,这似乎不再起作用,因为在标签为“gpu”的节点上执行了多个具有“CUDA”类别的作业。

        1. Global.png
          Global.png
          9 kB
        2. Job.png
          Job.png
          5 kB

          [JENKINS-20211] Pairs of throttled node labels no longer seem to work starting from version 1.536

          Daniel Beck added a comment -

          Anyone still able to reproduce this issue on recent Jenkins + Plugin versions?

          Daniel Beck added a comment - Anyone still able to reproduce this issue on recent Jenkins + Plugin versions?

          I am currently seeing this issue.
          Jenkins 1.609 with Throttle 1.8.4

          I have read that 'Priority Sort Plugin' can cause issues with Throttle. I have Priority 2.9.

          I have tried several different configurations. I don't see anything that is working. I think that throttling per project is working but have not been able to confirm it. I have tired setting the max per label. I have tried without setting a max per label. Nothing seems to work.

          Dwane Pottratz added a comment - I am currently seeing this issue. Jenkins 1.609 with Throttle 1.8.4 I have read that 'Priority Sort Plugin' can cause issues with Throttle. I have Priority 2.9. I have tried several different configurations. I don't see anything that is working. I think that throttling per project is working but have not been able to confirm it. I have tired setting the max per label. I have tried without setting a max per label. Nothing seems to work.

          Peter Triesz added a comment -

          We also experience this. We have several Multi-configuration projects and we use several Multi-Project Throttle Categories. Throttling config worked originally but lately executions stopped respecting these constraints.

          We have upgraded to Jenkins 1.609 with Throttle 1.8.4 but the issue still persists.
          We tried throttling on global level and leave 0 in the project configs, as well as setting 1 everywhere but none of the setting combinations worked.
          We do not use the Priority Sort Plugin.

          Peter Triesz added a comment - We also experience this. We have several Multi-configuration projects and we use several Multi-Project Throttle Categories. Throttling config worked originally but lately executions stopped respecting these constraints. We have upgraded to Jenkins 1.609 with Throttle 1.8.4 but the issue still persists. We tried throttling on global level and leave 0 in the project configs, as well as setting 1 everywhere but none of the setting combinations worked. We do not use the Priority Sort Plugin.

          I still see this issue with Priority 2.12.

          Dwane Pottratz added a comment - I still see this issue with Priority 2.12.

          I have seen this issue as well. I just upgraded from 1.522 to 1.608. We're using an old Throttle plugin, 1.7.2, but it appears from the previous comments that this won't fix it.

          I was able to figure out that the problem occurs when 2 jobs that are supposed to throttle under the same category are started at exactly the same time. I created a job that started two jobs when completed. All three run with the same throttle category on the same node. The two child jobs will be started simultaneously when one should block the other.

          Hope this helps.

          Christopher Carlson added a comment - I have seen this issue as well. I just upgraded from 1.522 to 1.608. We're using an old Throttle plugin, 1.7.2, but it appears from the previous comments that this won't fix it. I was able to figure out that the problem occurs when 2 jobs that are supposed to throttle under the same category are started at exactly the same time. I created a job that started two jobs when completed. All three run with the same throttle category on the same node. The two child jobs will be started simultaneously when one should block the other. Hope this helps.

          Daniel Beck added a comment -

          Possibly related to the queue concurrency issue introduced in 1.536 or so. Apparently it's easiest to see when you only have one CPU core, no hyperthreading. That was resolved in 1.607, with further fixes in 1.610 (no changelog entry for that yet).

          Daniel Beck added a comment - Possibly related to the queue concurrency issue introduced in 1.536 or so. Apparently it's easiest to see when you only have one CPU core, no hyperthreading. That was resolved in 1.607, with further fixes in 1.610 (no changelog entry for that yet).

          Looks to be working in 1.610

          Dwane Pottratz added a comment - Looks to be working in 1.610

          Daniel Beck added a comment -

          Anyone still experiencing this issue on 1.610+?

          Daniel Beck added a comment - Anyone still experiencing this issue on 1.610+?

          Peter Triesz added a comment -

          with 1.610 throttling started to work again for us. YEY. thanks a bunch.

          Peter Triesz added a comment - with 1.610 throttling started to work again for us. YEY. thanks a bunch.

          Daniel Beck added a comment -

          Assuming to be a duplicate of one of the recent queue processing fixes.

          Daniel Beck added a comment - Assuming to be a duplicate of one of the recent queue processing fixes.

            abayer Andrew Bayer
            simabeis Marcel Beister
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: