Uploaded image for project: 'JS - JobScheduler'
  1. JS - JobScheduler
  2. JS-1516

Enqueued tasks are not started when a process class with a limit is assigned to more than one job

    XMLWordPrintable

    Details

    • Type: Fix
    • Status: Released (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.10.1
    • Fix Version/s: 1.10.2, 1.11
    • Component/s: None
    • Labels:
      None

      Description

      Current Situation

      • We assume that we have two jobs which are used with the same process class.
      • The jobs can start more than one task in parallel but the process class has the limit max_processes=1.
      • The first job is started (manually) and while this task is running the second job is started and the first job is started once more.
      • Then both jobs get the status waiting_for_process="yes" because of the process class limit and the job starts are enqueued.
      • If the first running task is finished then
        • none of the enqueued tasks are started
        • the second job has still the status waiting_for_process="yes"
        • every further job start are only enqueued and not started even if the task queue was cleared before.

      Desired Behavior

      • Enqueued tasks should be started

      Workaround

      • Modify the max. number of tasks in the process class to a value that is not reached.
      • Example:
             <process_class  max_processes="100"/>
        

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jz Joacim Zschimmer
                Reporter:
                oh Oliver Haufe
                Approver:
                Oliver Haufe
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: