Bug 2130276
| Summary: | The scheduled time of the changelog compaction is not taken into account. | ||
|---|---|---|---|
| Product: | Red Hat Directory Server | Reporter: | Têko Mihinto <tmihinto> |
| Component: | 389-ds-base | Assignee: | mreynolds |
| Status: | CLOSED ERRATA | QA Contact: | LDAP QA Team <idm-ds-qe-bugs> |
| Severity: | medium | Docs Contact: | Evgenia Martynyuk <emartyny> |
| Priority: | high | ||
| Version: | 11.5 | CC: | bsmejkal, bugzilla-redhat, emartyny, idm-ds-dev-bugs, mreynolds, mschwabe, pasik, tbordaz, vcech |
| Target Milestone: | DS11.7 | Keywords: | TestCaseProvided, Triaged |
| Target Release: | dirsrv-11.7 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | sync-to-jira | ||
| Fixed In Version: | redhat-ds-11-8080020221130182235.022a399e | Doc Type: | Bug Fix |
| Doc Text: |
.The scheduled time of the changelog compaction now works correctly
Previously, when you configured a custom scheduled time for the changelog compaction, the server did not apply the new setting, and the changelog compaction could start during peak times. With this release, the server now correctly applies the custom time of the changelog compaction.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-05-23 09:27:55 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Têko Mihinto
2022-09-27 16:42:07 UTC
The compaction starts at the expected time when the nsslapd-changelogcompactdb-time is unset ( thus using the default value of 23:59 ): grep -i compa /var/log/dirsrv/slapd-localhost/errors* /var/log/dirsrv/slapd-localhost/errors.20221002-000222:[02/Oct/2022:23:59:27.161439332 +0200] - NOTICE - NSMMReplicationPlugin - changelog program - cl5CompactDBs - compacting replication changelogs... /var/log/dirsrv/slapd-localhost/errors.20221002-000222:[02/Oct/2022:23:59:32.867428009 +0200] - NOTICE - NSMMReplicationPlugin - changelog program - cl5CompactDBs - compacting replication changelogs finished. /var/log/dirsrv/slapd-localhost/errors.20221004-000154:[04/Oct/2022:23:59:01.988719414 +0200] - NOTICE - NSMMReplicationPlugin - changelog program - cl5CompactDBs - compacting replication changelogs... /var/log/dirsrv/slapd-localhost/errors.20221004-000154:[04/Oct/2022:23:59:22.602587530 +0200] - NOTICE - NSMMReplicationPlugin - changelog program - cl5CompactDBs - compacting replication changelogs finished. /var/log/dirsrv/slapd-localhost/errors.20221006-000152:[06/Oct/2022:23:59:25.458998883 +0200] - NOTICE - NSMMReplicationPlugin - changelog program - cl5CompactDBs - compacting replication changelogs... /var/log/dirsrv/slapd-localhost/errors.20221006-000152:[06/Oct/2022:23:59:25.870496531 +0200] - NOTICE - NSMMReplicationPlugin - changelog program - cl5CompactDBs - compacting replication changelogs finished. I think I know what is going on. The issue is the compaction interval. It's set to 2 days, but the way it works is that it's two days (48 hours) from the time the server "starts". It's just a timer. So if the server was restarted at 8:00, then the trim/compact thread is not going to wake up until 8:00 two days later. It wakes up, and sees that it's past the 2:00 TOD setting and thinks it must compact. The reason why 11:59 works is because it's at the very end of the day. When the time is early in the day then this can break. Continuing investigation... Fixed upstream: https://github.com/389ds/389-ds-base/issues/5532 Hi Mark! Could you please review the DocText field with the RN text draft. Thanks, Evgenia (In reply to Evgenia Martynyuk from comment #22) > Hi Mark! > > Could you please review the DocText field with the RN text draft. > > Thanks, > Evgenia Looks good RN passed a peer review, RN text is release pending Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (redhat-ds:11 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:3267 |