Uploaded image for project: 'CDAP'
  1. CDAP
  2. CDAP-15109

Max concurrent runs in a schedule does not consider PENDING state

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.1.2
    • Fix Version/s: 6.0.0
    • Component/s: App Fabric
    • Labels:
      None
    • Rank:
      1|i00mcv:

      Description

      I have 5 pipelines scheduled to run every minute with a max concurrent run of 1 for each pipeline. Each run provisions a cluster and then runs the pipeline.

      At any point in time, I don't expect more than 5 clusters to be provisioned due to the max concurrent runs constraint. However, the max concurrent runs only considers RUNNING state, whereas a program will be in PENDING state during provisioning. This leads to multiple active runs for a given pipeline that has a max concurrent run of 1. In this particular case, there were more than 20 clusters provisioned at a given time.

        Attachments

          Activity

            People

            • Assignee:
              poorna Poorna Chandra
              Reporter:
              poorna Poorna Chandra
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: