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

Avoid unneccessary creation of new IDs for table SCHEDULER_HISTORY when using a non-distributed job chain with a file order source

    XMLWordPrintable

Details

    • Fix
    • Status: Released (View Workflow)
    • Major
    • Resolution: Fixed
    • 1.7, 1.8
    • 1.7.6, 1.8.3, 1.9
    • None
    • None

    Description

      Description

      • When running a job chain with a file order source, there are many unnecessary creations of new IDs observed that result in high CPU load of the database server.The maximum number observed has been 30000 IDs.
      • This behavior is visible from the log by repeated execution of the statement: 
        UPDATE SCHEDULER_VARIABLES  set `wert`=`wert`+1  where `name`='spooler_job_id

      Desired Behaviour

      • A new ID for the table SCHEDULER_HISTORY should only be created when required.

      Debug Info

      • To reproduce this, create a job chain with a file order source. When a file arrives there are many log lines created like this: 
        .17 14:45:44.471 scheduler    0  9168.3358 3651.832MB .{scheduler} sos::scheduler::database::Transaction::execute  COMMIT  (sos::scheduler::database::Database::get_id_)
.17 14:45:44.487 scheduler   16  9168.3358 3651.832MB .{scheduler} sos::scheduler::database::Transaction::execute  UPDATE SCHEDULER_VARIABLES  set `wert`=`wert`+1  where `name`='spooler_job_id'  (sos::scheduler::database::Database::get_id_)

      Attachments

        Issue Links

          affects

          Fix - JS-1390 <file_order_source> should not fall asleep after the first files

          • Blocker - Blocks development and/or testing work, production could not run.
          • Released

          Fix - JS-1391 Resumption of "Avoid unneccessary creation of new IDs for table SCHEDULER_HISTORY when using a non-distributed job chain with a file order source" for use with the max_orders attribute

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

          Fix - JS-1606 Resumption of "Avoid unneccessary creation of new IDs for table SCHEDULER_HISTORY when using a non-distributed job chain with a file order source" when two job chain monitors the same directory with the same filter

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Known Issue
          is related to

          Fix - JS-1381 Avoid unneccessary creation of new ids for table scheduler_history when using a distributed job chain

          • Major - Major loss of function.
          • Approved

          Fix - JS-1688 For Stopped File order source job chain JobScheduler creates unnecessary Job_Ids

          • Major - Major loss of function.
          • Released

          Activity

            People

              jz Joacim Zschimmer
              ur Uwe Risse
              Uwe Risse Uwe Risse
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: