comparison Sphinx/source/users/advanced-rest.rst @ 854:b569e93d1d45

jobs update
author Alain Mazy <am@osimis.io>
date Wed, 08 Jun 2022 16:35:11 +0200
parents 989f00cd4dfa
children 12f8932ee3a7
comparison
equal deleted inserted replaced
853:2d9024137da0 854:b569e93d1d45
15 15
16 Jobs 16 Jobs
17 ---- 17 ----
18 18
19 Since Orthanc 1.4.0, a jobs engine is embedded within Orthanc. Jobs 19 Since Orthanc 1.4.0, a jobs engine is embedded within Orthanc. Jobs
20 are high-level tasks to be processed by Orthanc. Jobs are first added 20 are high-level tasks to be processed by Orthanc. Jobs can be started
21 synchronously or asynchronously (see the section below). All Jobs,
22 no matter how they were started, are first added
21 to a queue of pending tasks, and Orthanc will simultaneously execute a 23 to a queue of pending tasks, and Orthanc will simultaneously execute a
22 fixed number of jobs (check out :ref:`configuration option 24 fixed number of jobs (check out :ref:`configuration option
23 <configuration>` ``ConcurrentJobs``). Once the jobs have been 25 <configuration>` ``ConcurrentJobs``). Once the jobs have been
24 processed, they are tagged as successful or failed, and kept in a 26 processed, they are tagged as successful or failed, and kept in a
25 history (the size of this history is controlled by the 27 history (the size of this history is controlled by the
26 ``JobsHistorySize`` option). 28 ``JobsHistorySize`` option).
27 29
28 By default, Orthanc saves the jobs into its database (check out the 30 By default, Orthanc saves the jobs into its database (check out the
29 ``SaveJobs`` option). Jobs are saved every 10 seconds and when 31 ``SaveJobs`` option). Jobs are saved every 10 seconds and when
30 Orthanc stops. If Orthanc is stopped then relaunched, the jobs 32 Orthanc stops. If Orthanc is stopped then relaunched, the jobs whose
31 whose processing was not finished are automatically put into the queue 33 processing was not finished are automatically put into the queue of
32 of pending tasks or resumed if they were being processed when Orthanc 34 pending tasks or resumed if they were being processed when Orthanc stopped,
33 stopped. The command-line option ``--no-jobs`` can also be used to 35 regardless of whether they were started synchronously or asynchronously
36 (see the section below). The command-line option ``--no-jobs`` can also be used to
34 prevent the loading of jobs from the database upon the launch of 37 prevent the loading of jobs from the database upon the launch of
35 Orthanc. 38 Orthanc.
36 39
37 Note that the queue of pending jobs has no size limit. 40 Note that the queue of pending jobs has no size limit.
38 41