Date: Thu, 28 Mar 2024 10:58:37 +0000 (UTC) Message-ID: <578617405.11381.1711623517681@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_11380_1078942244.1711623517681" ------=_Part_11380_1078942244.1711623517681 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
We have a linear job chain of jobs - 1,2,3. I kill JobScheduler after Jo= b1 is complete but while Job2 is still running and then start the scheduler= back up. If we then re-start the job chain, will it start at Job2?
Yes, the order will be enqueued with a state for Job2. This applies to b= oth orders and jobs:
If an order is enqueued (either for on= e time processing without any run time or with a run time for repeated proc= essing) then JobScheduler stores this order in the database (in the table <= code>SCHEDULER_ORDERS).
Changes to the order state that reflec= t the proceeding of the order in the job chain to the next job node are equ= ally updated in the database. To be transactionally correct the order state= is updated after
spooler_process()
is completed for jobs that ma=
ke use of the API via <script language=3D"Java|java:JavaScript"/&g=
t;
<script language=3D"shell"/>
If JobScheduler is killed while an order is processed then the orde= r with it's current state, i.e. the input level of the current job node, wi= ll be restored from the database on the next start of the JobScheduler.
=This is handled in the following way:
<start_=
job job=3D"..." at=3D"now+3600"/><params/></start_job>
or the respective API methods then this task's start time is reflected in=
the database (in the table SCHEDULER_TASKS
). For orders and j=
obs JobScheduler will read the respective tables on startup and enqueue the=
respective orders and task to the given start time.