Mercurial > hg > orthanc-book
comparison Sphinx/source/plugins/postgresql.rst @ 438:5d6d593bceb6
scalability section
| author | Alain Mazy <alain@mazy.be> |
|---|---|
| date | Tue, 26 May 2020 08:21:29 +0200 |
| parents | c95817c254fe |
| children | 987fbbc2b59e |
comparison
equal
deleted
inserted
replaced
| 436:0942c745d2b5 | 438:5d6d593bceb6 |
|---|---|
| 241 | 241 |
| 242 Obviously, one must be very cautious when sharing the same database | 242 Obviously, one must be very cautious when sharing the same database |
| 243 between instances of Orthanc. In particular, all these instances | 243 between instances of Orthanc. In particular, all these instances |
| 244 should share the same configuration. | 244 should share the same configuration. |
| 245 | 245 |
| 246 Furthermore, the core of Orthanc does not currently support the replay | |
| 247 of database transactions, which is necessary to deal with conflicts | |
| 248 between several instances of Orthanc that would simultaneously write | |
| 249 to the database. | |
| 250 | |
| 251 As a consequence, as of Orthanc 1.7.0, when connecting multiple | |
| 252 Orthanc to a single database by setting ``Lock`` to ``false``, there | |
| 253 should only be one instance of Orthanc acting as a writer and all the | |
| 254 other instances of Orthanc acting as readers only. Be careful to set | |
| 255 the option ``SaveJobs`` to ``false`` in the configuration file of all | |
| 256 the instances of Orthanc acting as readers. | |
| 257 | |
| 258 A refactoring is needed to improve the core of Orthanc in that | |
| 259 respect, for which we are looking for funding/donation from the | |
| 260 industry. Some issues reported in our bug tracker call for this | |
| 261 refactoring: `issue 83 | |
| 262 <https://bitbucket.org/sjodogne/orthanc/issues/83/>`__, `issue 121 | |
| 263 <https://bitbucket.org/sjodogne/orthanc/issues/121/>`__, `issue 151 | |
| 264 <https://bitbucket.org/sjodogne/orthanc/issues/151/>`__. | |
| 265 | |
| 266 | |
| 267 | 246 |
| 268 Keep-alive | 247 Keep-alive |
| 269 ^^^^^^^^^^ | 248 ^^^^^^^^^^ |
| 270 | 249 |
| 271 .. highlight:: text | 250 .. highlight:: text |
| 281 | 260 |
| 282 This is due to a timeout in the PostgreSQL server. Please make sure to | 261 This is due to a timeout in the PostgreSQL server. Please make sure to |
| 283 `enable keep-alive | 262 `enable keep-alive |
| 284 <https://dba.stackexchange.com/questions/97534/is-there-a-timeout-option-for-remote-access-to-postgresql-database>`__ | 263 <https://dba.stackexchange.com/questions/97534/is-there-a-timeout-option-for-remote-access-to-postgresql-database>`__ |
| 285 in the configuration of your PostgreSQL server | 264 in the configuration of your PostgreSQL server |
| 265 | |
| 266 | |
| 267 Scalability | |
| 268 ^^^^^^^^^^^ | |
| 269 | |
| 270 When configuring your PostgreSQL plugin, ensure you've read the :ref:`scalability section | |
| 271 <scalability>` |