Back to bug 1314557
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Noriko Hosoi | 2016-03-03 22:24:58 UTC | Status | NEW | POST |
| 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. |
|||
| Jan Kurik | 2016-03-07 07:34:18 UTC | Blocks | 1315181 | |
| Jan Kurik | 2016-03-07 07:34:41 UTC | Keywords | ZStream | |
| Lenka Špačková | 2016-03-18 08:16:30 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:29:27 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. |
| Sat6QE Jenkins | 2016-03-28 20:15:54 UTC | Status | POST | MODIFIED |
| Mike McCune | 2016-03-28 23:13:32 UTC | Status | MODIFIED | POST |
| Noriko Hosoi | 2016-05-04 19:47:35 UTC | Status | POST | MODIFIED |
| Fixed In Version | 389-ds-base-1.3.5.2-1.el7 | |||
| errata-xmlrpc | 2016-05-04 20:08:45 UTC | Status | MODIFIED | ON_QA |
| Petr Bokoc | 2016-07-27 13:01:26 UTC | CC | pbokoc | |
| Doc Text | 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. | Change in keep alive entry log level 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. At the same time, each entry is tested to see if it exists before the update. This test was previously logged at a `Fatal` log level, so it was logged no matter which log level had been set. Consequently, error logs were filled with unnecessary messages which could not be filtered out. This update changes the log level for keep alive entry testing from `Fatal` to `Replication debugging` (`8192`), which means these entries can now be easily filtered and the error log file is no longer filled with `Fatal` messages. |
||
| Petr Bokoc | 2016-07-27 13:05:11 UTC | Doc Text | Change in keep alive entry log level 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. At the same time, each entry is tested to see if it exists before the update. This test was previously logged at a `Fatal` log level, so it was logged no matter which log level had been set. Consequently, error logs were filled with unnecessary messages which could not be filtered out. This update changes the log level for keep alive entry testing from `Fatal` to `Replication debugging` (`8192`), which means these entries can now be easily filtered and the error log file is no longer filled with `Fatal` messages. | Change in keep alive entry log level 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. At the same time, each entry is tested to see if it already exists before the update in order to avoid creating the same entry more than once. This test was previously logged at a `Fatal` log level, which caused error logs to be filled with unnecessary messages which could not be filtered out. This update changes the log level for keep alive entries from `Fatal` to `Replication debugging` (`8192`), and the entries can now be filtered out. |
| Petr Bokoc | 2016-07-27 13:34:25 UTC | Docs Contact | pbokoc | |
| Petr Bokoc | 2016-08-19 14:50:42 UTC | Doc Text | Change in keep alive entry log level 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. At the same time, each entry is tested to see if it already exists before the update in order to avoid creating the same entry more than once. This test was previously logged at a `Fatal` log level, which caused error logs to be filled with unnecessary messages which could not be filtered out. This update changes the log level for keep alive entries from `Fatal` to `Replication debugging` (`8192`), and the entries can now be filtered out. | Change in keep alive entry logging level Keep alive entries are used to prevent skipped updates from being evaluated multiple times in fractional replication. If a large number of updates is skipped, these entries can be updated very frequently. Also, each entry is tested to see if it already exists before the update, so that only unique entries are created. This test was previously logged at the `Fatal` level, which caused error logs to be filled with unnecessary messages that could not be filtered out. This update changes the logging level for keep alive entries from `Fatal` to `Replication debugging` (`8192`), and the entries can now be filtered out. |
| Viktor Ashirov | 2016-08-27 16:54:00 UTC | Status | ON_QA | VERIFIED |
| errata-xmlrpc | 2016-11-02 12:25:00 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-11-03 20:39:53 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-11-03 16:39:53 UTC | |||
| Simon Pichugin | 2020-09-13 21:38:37 UTC | Link ID | Github 389ds/389-ds-base/issues/1751 |
Back to bug 1314557