Skip to content

Commit 391c37c

Browse files
changed solution to be more generic, added note for docker installations
1 parent 3013bb3 commit 391c37c

1 file changed

Lines changed: 2 additions & 4 deletions

File tree

doc/sphinx-guides/source/installation/config.rst

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -966,13 +966,11 @@ Database Connection Recovery
966966
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
967967

968968
Consider the following scenario: if there is no advanced configuration for the database connection and the Dataverse server loses that connection, for example if the database host is down, the server will be "dead" even after the database server is back to normal.
969-
The only solution to recover Dataverse would be to restart the service and redeploy the application. To avoid this situation, a simple init.d script can be created with the following settings that configure validation of the database connection.
970-
This way, the database connection can be automatically recovered after a failure, improving the server availability.
969+
The only solution to recover Dataverse would be to restart the service and redeploy the application. To avoid this situation, the following settings can be used to configure validation of the database connection.
970+
This way, the database connection can be automatically recovered after a failure, improving the server availability. For a Docker installation, it is suggested to create an init.d script so that if the container needs to be recreated, these settings will always be configured.
971971

972972
.. code-block:: bash
973973
974-
#!/bin/bash
975-
976974
# Enable database connection validation
977975
asadmin create-jvm-options "-Ddataverse.db.is-connection-validation-required=true"
978976
# Configure to use a database table as the validation method

0 commit comments

Comments
 (0)