From: Razvan Becheriu Date: Wed, 9 Dec 2020 17:09:25 +0000 (+0200) Subject: [#1375] updated ChangeLog and documentation X-Git-Tag: Kea-1.9.3~72 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ecc2afeae55486a96c900446a8937608dbbe6ee7;p=thirdparty%2Fkea.git [#1375] updated ChangeLog and documentation --- diff --git a/ChangeLog b/ChangeLog index 90fc7129ab..e64644f75a 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,13 @@ +1842. [bug] razvan + Fixed the db connection reconnect implemenation to honor + each connection backend configuration. The most important + improvement is that only the affected mananger will be + recreated when a connection is lost. Previously, even + managers which were not affected had to be recreated on + any connection loss. Also fixed an issue with recovery + when multi-threading is enabled. + (Gitlab #1375) + 1841. [bug] marcin Corrected issues with inheritance of the DHCPv6 interface-id parameter. When interface-id is set at shared network level diff --git a/doc/sphinx/arm/database-connectivity.rst b/doc/sphinx/arm/database-connectivity.rst index 5b63588638..ee553e54ab 100644 --- a/doc/sphinx/arm/database-connectivity.rst +++ b/doc/sphinx/arm/database-connectivity.rst @@ -26,9 +26,9 @@ up. It is able to process commands but does not serve clients. This 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 all backends and then attempts to reconnect. During the recovery -process, the server ceases to serve clients but 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. +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 but 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.