>> Hmm... so would you recommend removing the replication of cn=config for
>> now? Individually adding the schema to each master is feasible for us.
>
> If it's not required then yes, I personally would not use it at this
> time. For example, ITS#8286, although it only discusses a single matching
> rule, ended up touching numerous files, and it's directly related to
> using cn=config and cn=config replication
> (<https://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commitdiff;h
> =3add82a3bb30b94afd23ff5e2c00c59ca8a931d8>).

To which I should add -- And is only being fixed for OpenLDAP 2.5 and later.