mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-08-22 09:57:41 +00:00
Code Issues Releases Wiki Activity

[#3019] remove limitation on db retry from doc

Browse Source
This commit is contained in:
Andrei Pavel 2024-05-17 12:07:47 +03:00
parent c85bdf4df2
commit 0186cbb31e
No known key found for this signature in database
GPG Key ID: D4E804481939CB21
4 changed files with 1 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/sphinx/arm/database-connectivity.rst
View File

@ -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 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 attempts even at server startup or on reconfigure events, and will honor the
action specified in the ``on-fail`` parameter. 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 During dynamic reconfiguration, all backends are disconnected and then
reconnected using the new configuration. If connectivity to any of the 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:: .. note::
Kea does not automatically attempt to upgrade an existing schema; doing so 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 backing up the database or temporarily shutting off running
Kea servers that are currently operating on the database. Kea servers that are currently operating on the database.

4
doc/sphinx/arm/dhcp4-srv.rst
View File

@ -825,10 +825,6 @@ system allows nanny scripts to detect the problem.
If ``retry-on-startup`` is set to ``true``, the server starts reconnection If ``retry-on-startup`` is set to ``true``, the server starts reconnection
attempts even at server startup or on reconfigure events, and honors the attempts even at server startup or on reconfigure events, and honors the
action specified in the ``on-fail`` parameter. 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 Finally, the credentials of the account under which the server will
access the database should be set: access the database should be set:

4
doc/sphinx/arm/dhcp6-srv.rst
View File

@ -781,10 +781,6 @@ system allows nanny scripts to detect the problem.
If ``retry-on-startup`` is set to ``true``, the server starts reconnection If ``retry-on-startup`` is set to ``true``, the server starts reconnection
attempts even at server startup or on reconfigure events, and honors the attempts even at server startup or on reconfigure events, and honors the
action specified in the ``on-fail`` parameter. 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 Finally, the credentials of the account under which the server will
access the database should be set: access the database should be set:

7
doc/sphinx/arm/hooks-limits.rst
View File

@ -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 respective client class or subnet. To reset the lease count, change the client class name
or the subnet ID. 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: .. _hooks-limits-lease-limiting:
Lease Limiting Lease Limiting