mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-08-31 14:05:33 +00:00
Code Issues Releases Wiki Activity

[#1621] disabling connection recovery mechanish is not available in core managers

Browse Source
This commit is contained in:
Razvan Becheriu
2021-03-24 08:19:00 +02:00
parent a7cb38305f
commit f525fc6335
17 changed files with 62 additions and 144 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -6,8 +6,8 @@ Database Connectivity
Kea servers (kea-dhcp4 and kea-dhcp6) can be configured to use a variety of
database backends for leases, hosts, and configuration. All of them may be
configured to support automatic recovery when connectivity is lost (see
``max-reconnect-tries``, ``reconnect-wait-time``, ``disable-dhcp-on-db-loss``
and ``enable-connection-recovery``).
``max-reconnect-tries``, ``reconnect-wait-time``and
``disable-service-on-db-loss``).
It is important to understand how and when automatic recovery comes into play.
Automatic recovery, when configured, only operates after a successful startup
@@ -29,15 +29,8 @@ allows the configuration to be corrected via command, if required.
During normal operations, if connectivity to any of the backends is lost and
automatic recovery for that backend is enabled, the server disconnects from the
respective backend and then attempts to reconnect. During the recovery process,
the server ceases to serve clients according to the ``disable-dhcp-on-db-loss``
configured option, and continues to respond to commands. If connectivity to all
backends is restored, the server returns to normal operations. If connectivity
cannot be restored after ``max-reconnect-tries``, the server issues a fatal
error and exits.
The entire database connection mechanism can be completely disabled by setting
``enable-connection-recovery`` to false. This will cause the server to ignore
the failure of the database connections and it is highly discouraged. This will
cause the server to not function properly and log errors. The default value for
``enable-connection-recovery`` is true. This feature is mainly used by hook
libraries which can function properly without permanent database connections.
the server ceases to serve clients according to the
``disable-service-on-db-loss`` configured option, and continues to respond to
commands. If connectivity to all backends is restored, the server returns to
normal operations. If connectivity cannot be restored after
``max-reconnect-tries``, the server issues a fatal error and exits.

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

@@ -506,18 +506,11 @@ loss of connectivity. The default value for Cassandra is 2000 ms.
::
"Dhcp4": { "lease-database": { "disable-dhcp-on-db-loss" : true, ... }, ... }
"Dhcp4": { "lease-database": { "disable-service-on-db-loss" : true, ... }, ... }
The default value for MySQL and PostgreSQL is true, which disables the dhcp
service while trying to automatically recover lost connections.
::
"Dhcp4": { "lease-database": { "enable-connection-recovery" : true, ... }, ... }
The default value for MySQL and PostgreSQL is true, which enables the server to
automatically recover lost connections.
.. note::
Automatic reconnection to database backends is configured
@@ -732,18 +725,11 @@ loss of connectivity. The default value for Cassandra is 2000 ms.
::
"Dhcp4": { "hosts-database": { "disable-dhcp-on-db-loss" : true, ... }, ... }
"Dhcp4": { "hosts-database": { "disable-service-on-db-loss" : true, ... }, ... }
The default value for MySQL and PostgreSQL is true, which disables the dhcp
service while trying to automatically recover lost connections.
::
"Dhcp4": { "hosts-database": { "enable-connection-recovery" : true, ... }, ... }
The default value for MySQL and PostgreSQL is true, which enables the server to
automatically recover lost connections.
.. note::
Automatic reconnection to database backends is configured

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

@@ -475,18 +475,11 @@ loss of connectivity. The default value for Cassandra is 2000 ms.
::
"Dhcp6": { "lease-database": { "disable-dhcp-on-db-loss" : true, ... }, ... }
"Dhcp6": { "lease-database": { "disable-service-on-db-loss" : true, ... }, ... }
The default value for MySQL and PostgreSQL is true, which disables the dhcp
service while trying to automatically recover lost connections.
::
"Dhcp6": { "lease-database": { "enable-connection-recovery" : true, ... }, ... }
The default value for MySQL and PostgreSQL is true, which enables the server to
automatically recover lost connections.
.. note::
Automatic reconnection to database backends is configured
@@ -651,18 +644,11 @@ loss of connectivity. The default value for Cassandra is 2000 ms.
::
"Dhcp6": { "hosts-database": { "disable-dhcp-on-db-loss" : true, ... }, ... }
"Dhcp6": { "hosts-database": { "disable-service-on-db-loss" : true, ... }, ... }
The default value for MySQL and PostgreSQL is true, which disables the dhcp
service while trying to automatically recover lost connections.
::
"Dhcp6": { "hosts-database": { "enable-connection-recovery" : true, ... }, ... }
The default value for MySQL and PostgreSQL is true, which enables the server to
automatically recover lost connections.
.. note::
Automatic reconnection to database backends is configured