Mercurial > hg > orthanc-book
comparison Sphinx/source/faq/scalability.rst @ 947:0b89127439b1
new orthanc-setup-samples repo
author | Alain Mazy <am@osimis.io> |
---|---|
date | Thu, 01 Jun 2023 12:24:22 +0200 |
parents | 49b863e47c39 |
children | 5df222ddd7d1 |
comparison
equal
deleted
inserted
replaced
946:d7f03f325544 | 947:0b89127439b1 |
---|---|
240 concurrent access to the DB. | 240 concurrent access to the DB. |
241 | 241 |
242 One solution to avoid this limitation was to have multiple Orthanc | 242 One solution to avoid this limitation was to have multiple Orthanc |
243 accessing the same DB (works only for MySQL and PostgreSQL) as | 243 accessing the same DB (works only for MySQL and PostgreSQL) as |
244 presented in this `sample | 244 presented in this `sample |
245 <https://bitbucket.org/osimis/orthanc-setup-samples/src/master/docker/multiple-orthancs-on-same-db/>`__. | 245 <https://github.com/orthanc-server/orthanc-setup-samples/src/master/docker/multiple-orthancs-on-same-db/>`__. |
246 However, this solution was only robust if there was **one single | 246 However, this solution was only robust if there was **one single |
247 "writer" Orthanc server** (i.e. only one Orthanc was modifying the | 247 "writer" Orthanc server** (i.e. only one Orthanc was modifying the |
248 database). Indeed, the core of Orthanc <= 1.9.1 did not support the | 248 database). Indeed, the core of Orthanc <= 1.9.1 did not support the |
249 replay of database transactions, which is necessary to deal with | 249 replay of database transactions, which is necessary to deal with |
250 conflicts between several instances of Orthanc that would | 250 conflicts between several instances of Orthanc that would |