Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1388135
Description of problem: In Ipa, we are using content syncronization plugin to let DNS component be aware of changes under "cn=dns" We had a bug already fixed to exclude ipaca backend from retro changelog: bz 1346321 this has helped to prevent some deadlocks. But there's still some improvement here. In ipa we have a high number of updates in some situations like provisioning users in environments with large static groups or/and compat plugin enabled. Each time an update is done to the db, a retro changelog operation is logged. I think we will improve performance a lot and have less issues (lots of issues with updates in the retro changelog are seen at customer side) if we could restrict, in IPA, the retro changelog operations to dns subtree only. We don't have many dns updates. I am asking here whether an enhancement is possible to restrict by DNS subtree. Instead of excluding "o=ipaca", the change will be similar but this time we need an include suffix clause: nsslapd-include-suffix: "cn=dns,...."
Metadata Update from @pvoborni: - Issue assigned to someone - Issue set to the milestone: FreeIPA 4.5
Metadata Update from @mbasti: - Issue close_status updated to: None - Issue set to the milestone: FreeIPA 4.5.1 (was: FreeIPA 4.5)
Metadata Update from @mbasti: - Issue set to the milestone: FreeIPA 4.5.2 (was: FreeIPA 4.5.1)
FreeIPA 4.5.1 has been released, moving to FreeIPA 4.5.2 milestone
Metadata Update from @tkrizek: - Issue set to the milestone: FreeIPA 4.5.3 (was: FreeIPA 4.5.2)
Metadata Update from @tkrizek: - Issue set to the milestone: FreeIPA 4.5.4 (was: FreeIPA 4.5.3)
Metadata Update from @tkrizek: - Issue assigned to tkrizek (was: someone)
Metadata Update from @tkrizek: - Issue set to the milestone: FreeIPA 4.5.5 (was: FreeIPA 4.5.4)
Metadata Update from @tkrizek: - Custom field on_review adjusted to https://github.com/freeipa/freeipa/pull/1189 - Issue set to the milestone: FreeIPA 4.5.4 (was: FreeIPA 4.5.5)
master:
ipa-4-5:
ipa-4-6:
Metadata Update from @tkrizek: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.