comparison Sphinx/source/faq/scalability.rst @ 1088:eaf09977e3e9

ReadCommitted
author Alain Mazy <am@orthanc.team>
date Mon, 01 Jul 2024 10:23:55 +0200
parents d2be251975d1
children
comparison
equal deleted inserted replaced
1087:faf18bfe89a0 1088:eaf09977e3e9
317 transactions** a certain number of times (waiting 100ms more between 317 transactions** a certain number of times (waiting 100ms more between
318 each retry), until the transactions succeed. The plugins provide an 318 each retry), until the transactions succeed. The plugins provide an
319 option to control the maximum number of retries. If the maximum 319 option to control the maximum number of retries. If the maximum
320 number of retries is exceeded, the ``503 Service Unavailable`` HTTP 320 number of retries is exceeded, the ``503 Service Unavailable`` HTTP
321 error is raised (server overloaded because of unsuccessful retries 321 error is raised (server overloaded because of unsuccessful retries
322 of concurrent transactions). 322 of concurrent transactions). Note that, since version 6.0 of the PostgreSQL
323 plugin, it is now possible to configure the ``TransactionMode`` to
324 ``ReadCommitted`` instead of the default ``Serializable`` mode to avoid
325 most of the transactions collisions. This option is not (yet) available
326 for the MySQL plugin.
323 327
324 * If a higher-level application **modifies metadata and/or 328 * If a higher-level application **modifies metadata and/or
325 attachments** in the presence of multiple writers, Orthanc provides 329 attachments** in the presence of multiple writers, Orthanc provides
326 a :ref:`revision mechanism <revisions>` to prevent concurrent 330 a :ref:`revision mechanism <revisions>` to prevent concurrent
327 updates. 331 updates.