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

trimLabels calling Cloud#canProvision too often

    • 2.321

      Since JENKINS-65308 was implemented, we got several reports of provisioning issue.

      In CloudBees, we've had for years an implementation of Cloud where {provision,canProvision} are implemented as remote calls. #canProvision should ideally return fast so we know it is not ideal, but this has gone really worse since JENKINS-65308 got implemented due to the increase of calls to Cloud#canProvision.

      Something like JENKINS-57578 would likely clarify the situation, however in the current state, when calling trimLabels as part of a local operation (such as adding or removing a node), it would help if we only processed labels related to added or removed node(s).

          [JENKINS-67099] trimLabels calling Cloud#canProvision too often

          Vincent Latombe created issue -
          Vincent Latombe made changes -
          Link New: This issue relates to JENKINS-57578 [ JENKINS-57578 ]
          Vincent Latombe made changes -
          Description Original: Since JENKINS-65308 was implemented, we got several reports of provisioning issue.

          In CloudBees, we've had for years an implementation of Cloud where \{provision,canProvision} are implemented as remote calls. {{#canProvision}} should ideally return fast so we know it is not ideal, but this has gone really worse since JENKINS-65308 got implemented due to the increase of calls to {{Cloud#canProvision}}.

          In fact,
          New: Since JENKINS-65308 was implemented, we got several reports of provisioning issue.

          In CloudBees, we've had for years an implementation of Cloud where \{provision,canProvision} are implemented as remote calls. {{#canProvision}} should ideally return fast so we know it is not ideal, but this has gone really worse since JENKINS-65308 got implemented due to the increase of calls to {{Cloud#canProvision}}.

          Something like JENKINS-57578 would likely clarify the situation, however in the current state, when calling trimLabels as part of a local operation (such as adding or removing a node), it would help if we only processed labels related to added or removed node(s).
          Vincent Latombe made changes -
          Assignee New: Vincent Latombe [ vlatombe ]
          Vincent Latombe made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Vincent Latombe made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Vincent Latombe made changes -
          Remote Link New: This issue links to "PR #5882 (Web Link)" [ 27211 ]
          Vincent Latombe made changes -
          Link New: This issue is caused by JENKINS-65308 [ JENKINS-65308 ]
          Mark Waite made changes -
          Released As New: 2.321
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Closed [ 6 ]
          Vincent Latombe made changes -
          Labels New: lts-candidate

            vlatombe Vincent Latombe
            vlatombe Vincent Latombe
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: