Mercurial > hg > orthanc-book

comparison Sphinx/source/users/advanced-rest.rst @ 855:12f8932ee3a7

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
jobs update
author Alain Mazy <am@osimis.io>
date Wed, 08 Jun 2022 16:58:44 +0200
parents b569e93d1d45
children 3e8a3a900e9e
comparison
equal deleted inserted replaced
854:b569e93d1d45 855:12f8932ee3a7
26 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
27 history (the size of this history is controlled by the 27 history (the size of this history is controlled by the
28 ``JobsHistorySize`` option). 28 ``JobsHistorySize`` option).
29 29
30 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
31 ``SaveJobs`` option). Jobs are saved every 10 seconds and when 31 ``SaveJobs`` option). Jobs are saved within 100ms after their creation,
32 and then, the whole jobs list, with their updated status, is saved every 10 seconds and when
32 Orthanc stops. If Orthanc is stopped then relaunched, the jobs whose 33 Orthanc stops. If Orthanc is stopped then relaunched, the jobs whose
33 processing was not finished are automatically put into the queue of 34 processing was not finished are automatically put into the queue of
34 pending tasks or resumed if they were being processed when Orthanc stopped, 35 pending tasks or resumed if they were being processed when Orthanc stopped,
35 regardless of whether they were started synchronously or asynchronously 36 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 37 (see the section below). The command-line option ``--no-jobs`` can also be used to