Back to bug 1313258

Who When What Removed Added
Noriko Hosoi 2016-03-01 17:48:23 UTC Status NEW POST
Noriko Hosoi 2016-03-01 23:41:37 UTC CC tbordaz
Noriko Hosoi 2016-03-03 21:03:35 UTC Doc Text Cause: "keep alive" entries are used to prevent fractional replication to evaluate several times the same skipped updates. This entry is created on the fly when two many evaluated updates have been skipped.

Consequence: This is a quite common situation and the messages fill the error log.

Fix: Change the log level to replication level

Result: The error log file is not filled with the message unless the log level is set to the replication log level.
Noriko Hosoi 2016-03-03 21:14:47 UTC Status POST MODIFIED
Fixed In Version 389-ds-base-1.2.11.15-74.el6
Noriko Hosoi 2016-03-03 21:17:33 UTC Priority unspecified urgent
Hardware Unspecified x86_64
OS Unspecified Linux
Severity unspecified urgent
errata-xmlrpc 2016-03-03 21:19:15 UTC Status MODIFIED ON_QA
Eugene Keck 2016-03-03 21:40:48 UTC CC ekeck
Noriko Hosoi 2016-03-03 22:23:09 UTC Blocks 1314557
Jaroslav Reznik 2016-03-04 10:59:25 UTC Blocks 1314729
Jaroslav Reznik 2016-03-04 10:59:50 UTC Keywords ZStream
Lenka Špačková 2016-03-18 08:14:59 UTC Doc Text Cause: "keep alive" entries are used to prevent fractional replication to evaluate several times the same skipped updates. This entry is created on the fly when two many evaluated updates have been skipped.

Consequence: This is a quite common situation and the messages fill the error log.

Fix: Change the log level to replication level

Result: The error log file is not filled with the message unless the log level is set to the replication log level.
Keep alive entries are used to prevent fractional replication by evaluating the same skipped updates several times. If a large number of updates has been skipped, these entries were previously being created very frequently and they were being logged at a "Fatal" log level, which caused them to always be logged no matter which log level has been set, filling error logs with unnecessary messages. With this update, the log level for keep alive entry creation has been changed from "Fatal" to "Replication debugging" (8192) and the error log file will no longer be filled with "Fatal" messages.
Lenka Špačková 2016-03-18 18:28:20 UTC Doc Text Keep alive entries are used to prevent fractional replication by evaluating the same skipped updates several times. If a large number of updates has been skipped, these entries were previously being created very frequently and they were being logged at a "Fatal" log level, which caused them to always be logged no matter which log level has been set, filling error logs with unnecessary messages. With this update, the log level for keep alive entry creation has been changed from "Fatal" to "Replication debugging" (8192) and the error log file will no longer be filled with "Fatal" messages. Keep alive entries are used to prevent skipped updates from being evaluated several times in a fractional replication. If a large number of updates is skipped, these entries can be updated very frequently. Before the keep alive entries are updated, it is tested that they exist. Previously, the test was being logged at a "Fatal" log level, so it was always logged no matter which log level had been set. As a consequence, error logs were filled with unnecessary messages. With this update, the log level for keep alive entry creation has been changed from "Fatal" to "Replication debugging" (8192), and the error log file is no longer filled with "Fatal" messages.
Amita Sharma 2016-03-29 12:37:24 UTC Status ON_QA VERIFIED
CC amsharma
Petr Bokoc 2016-04-22 13:47:58 UTC CC pbokoc
Docs Contact pbokoc
errata-xmlrpc 2016-05-09 15:59:29 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-05-10 19:23:06 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-05-10 15:23:06 UTC
Simon Pichugin 2020-09-13 21:38:32 UTC Link ID Github 389ds/389-ds-base/issues/1751

Back to bug 1313258