[#1375] updated ChangeLog and documentation

diff --git a/ChangeLog b/ChangeLog
index 90fc7129abfe0a607633204ec1deeecdfbf8cec0..e64644f75a314ee30993f031e174a80d3de8d8a6 100644 (file)
--- 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 5b63588638d27f21add3f80ef8c27b04be374eb1..ee553e54ab30c8925df2559bc4278f2806d2d367 100644 (file)
--- 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.