From: Andrei Pavel Date: Fri, 17 May 2024 09:07:47 +0000 (+0300) Subject: [#3019] remove limitation on db retry from doc X-Git-Tag: Kea-2.6.0~71 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0186cbb31e078b9507dd4f59e38683925fdcf6a0;p=thirdparty%2Fkea.git [#3019] remove limitation on db retry from doc --- diff --git a/doc/sphinx/arm/database-connectivity.rst b/doc/sphinx/arm/database-connectivity.rst index 0050d596a2..0f5f2e2a48 100644 --- a/doc/sphinx/arm/database-connectivity.rst +++ b/doc/sphinx/arm/database-connectivity.rst @@ -24,10 +24,6 @@ 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 the ``on-fail`` parameter. -Database connection retries are not attempted on startup if the -:ischooklib:`libdhcp_limits.so` is loaded, because the hook library requires a -valid connection to the database to check whether JSON format is supported and to -recount class limits. During dynamic reconfiguration, all backends are disconnected and then reconnected using the new configuration. If connectivity to any of the @@ -69,7 +65,7 @@ as read-only, Kea attempts to initialize the schema. .. note:: Kea does not automatically attempt to upgrade an existing schema; doing so - might deprive users of the opportunity to take precautions, such as + might deprive users of the opportunity to take precautions, such as backing up the database or temporarily shutting off running Kea servers that are currently operating on the database. diff --git a/doc/sphinx/arm/dhcp4-srv.rst b/doc/sphinx/arm/dhcp4-srv.rst index b6c5e13a8b..f5e9da63b2 100644 --- a/doc/sphinx/arm/dhcp4-srv.rst +++ b/doc/sphinx/arm/dhcp4-srv.rst @@ -825,10 +825,6 @@ system allows nanny scripts to detect the problem. If ``retry-on-startup`` is set to ``true``, the server starts reconnection attempts even at server startup or on reconfigure events, and honors the action specified in the ``on-fail`` parameter. -Database connection retries are not attempted on startup if the -:ischooklib:`libdhcp_limits.so` is loaded, because the hook library requires a -valid connection to the database to verify whether JSON format is supported and to -recount class limits. Finally, the credentials of the account under which the server will access the database should be set: diff --git a/doc/sphinx/arm/dhcp6-srv.rst b/doc/sphinx/arm/dhcp6-srv.rst index f46484c7c7..cb4883fa8d 100644 --- a/doc/sphinx/arm/dhcp6-srv.rst +++ b/doc/sphinx/arm/dhcp6-srv.rst @@ -781,10 +781,6 @@ system allows nanny scripts to detect the problem. If ``retry-on-startup`` is set to ``true``, the server starts reconnection attempts even at server startup or on reconfigure events, and honors the action specified in the ``on-fail`` parameter. -Database connection retries are not attempted on startup if the -:ischooklib:`libdhcp_limits.so` is loaded, because the hook library requires a -valid connection to the database to verify whether JSON format is supported and to -recount class limits. Finally, the credentials of the account under which the server will access the database should be set: diff --git a/doc/sphinx/arm/hooks-limits.rst b/doc/sphinx/arm/hooks-limits.rst index a836da6817..73c6d2773b 100644 --- a/doc/sphinx/arm/hooks-limits.rst +++ b/doc/sphinx/arm/hooks-limits.rst @@ -117,13 +117,6 @@ This is how a lease limit is defined for a subnet inside a shared network: respective client class or subnet. To reset the lease count, change the client class name or the subnet ID. -.. note:: - - If :ischooklib:`libdhcp_limits.so` is loaded, database connection retries are not attempted - on startup. The hook library requires a - valid connection to the database to check whether JSON format is supported and to - recount class limits. - .. _hooks-limits-lease-limiting: Lease Limiting