diff options
Diffstat (limited to 'doc/sphinx/arm/database-connectivity.rst')
| -rw-r--r-- | doc/sphinx/arm/database-connectivity.rst | 17 |
1 files changed, 10 insertions, 7 deletions
diff --git a/doc/sphinx/arm/database-connectivity.rst b/doc/sphinx/arm/database-connectivity.rst index 12d9df7510..44f8208bc1 100644 --- a/doc/sphinx/arm/database-connectivity.rst +++ b/doc/sphinx/arm/database-connectivity.rst @@ -6,9 +6,9 @@ Database Connectivity The Kea servers (:iscman:`kea-dhcp4` and :iscman:`kea-dhcp6`) can be configured to use a variety of database backends for leases, hosts, and configuration. They can be configured to support automatic recovery when connectivity is lost, via -the ``on-fail`` parameter. (The ``reconnect-wait-time`` and -``max-reconnect-tries`` parameters are described -in :ref:`database-configuration4` and :ref:`database-configuration6`.) +the ``on-fail`` and ``retry-on-startup`` parameters. +(The ``reconnect-wait-time`` and ``max-reconnect-tries`` parameters are +described in :ref:`database-configuration4` and :ref:`database-configuration6`.) It is important to understand how and when automatic recovery comes into play. Automatic recovery, when configured, only operates after a successful startup @@ -16,10 +16,13 @@ or reconfiguration during which connectivity to all backends has been successfully established. During server startup, the inability to connect to any of the configured -backends is always considered fatal. A fatal error is logged and the server -exits, based on the idea that the configuration should be valid -at startup. Exiting to the operating system allows nanny scripts to detect -the problem. +backends is considered fatal only if ``retry-on-startup`` is set to ``false``. +A fatal error is logged and the server exits, based on the idea that the +configuration should be valid at startup. Exiting to the operating system allows +nanny scripts to detect the problem. +If ``retry-on-startup`` is set to ``true``, the server will start reconnection +attempts even at server startup or on reconfigure events, and will honor the +action specified in ``on-fail`` parameter. During dynamic reconfiguration, all backends are disconnected and then reconnected using the new configuration. If connectivity to any of the |