Hi,
Reading our docs, I see something ambiguous:
https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/Configuration_Command_and_File_Reference/Core_Ser
ver_Configuration_Reference.html#cnchangelog5
3.1.2.2. nsslapd-changelogmaxage (Max Changelog Age)
In the scenario where we have a replica that is offline, how does the changelog handle this?
Do we:
A) Trim the changelog, and expect the offline master to be re-initialised
B) Do we keep the event in the changelog even though it's expired maxage.
I think it would be good to clarify this behaviour in our documentation, but I wanted to know how it behaves first.
Thanks,
--
Sincerely,
William Brown
Software Engineer
Red Hat, Brisbane
No comments:
Post a Comment