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

Parallel job execution in job chain should not hang at parallel nodes if max_orders=1

    XMLWordPrintable

Details

    • Fix
    • Status: Released (View Workflow)
    • Major
    • Resolution: Duplicate
    • 1.5.3253
    • 1.7.4
    • Job Scheduler Binaries
    • None
    • JobScheduler Version 1.5.3253

    Description

      originally vg has found the bug

      If Job_Chain has the jobs configured to execute in parallel , with Splitter and Synch job,and If Job_Chain parameter MAX_ORDERS is set to 1 i.e. MAX_ORDERS=1, Job_Chain execution is hanging after the splitter node.

      • user given order is successfully splitted into three Orders
      • Log file is showing total 4 orders with correct Order name i.e. original_order+job_node_name

      Attachments

        1. job_chain3.zip
          3 kB
        2. job_chain_stopped.png
          job_chain_stopped.png
          16 kB

        Issue Links

          duplicates

          Feature - A feature of the product, which has yet to be developed. JS-1103 API method "ignore_max_orders" for orders

          • Major - Major loss of function.
          • Released

          Fix - JS-1207 In a nested job chain, the attribute max_orders does not work in inner job chains

          • Major - Major loss of function.
          • Released

          Fix - JS-1198 In a nested job chain, max_order in super chain limits order for the whole nested chain

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Released

          Activity

            People

              mp Mahendra Patidar
              mp Mahendra Patidar
              Mahendra Patidar Mahendra Patidar
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: