Schema Replication

[Scott Heger]

I see in the OpenDJ Admin Guide where it states:

OpenDJ also replicates schema definitions, so the schema you add on one replica is propagated to other replicas without you having to intervene manually.

Is that automatic whenever you enable replication for any baseDN or is there anything else that needs to be done? Also, when schema replication occurs, should an update to 99-user.ldif be reflected on all replicated servers at the time replication occurs or is there some other event that triggers that?

[Ludo]

Hi Scott,

Schema replication is enabled as soon as Replication is enabled between 2 servers, as there is a single global schema per server.
There are 2 events that are triggering schema replication :
– Schema is added online, using LDAP (modify). Unless specifically specified, these schema elements are written to the 99-user.ldif file and replicated to all servers in the same file.
– Schema files are added or altered while the server is offline. When starting, the server will notice that schema files have changed and the server will compute all changes, including the files in which these elements are stored, and will push the changes to their respective files on the replicated server.

The only thing that the server doesn’t do, is detecting changes in the schema files while the server is online, because the server is only expecting to write to those files new changes.

I hope this helps.

[Scott Heger]

Hi Ludo,

Yes, that helps very much and clarifies the process. We are working in replicated environment where as we bring on new clients into the system we need to bring in custom objectclasses/attributes. We are developing our process to handle these periodic schema updates to all OpenDJ servers. Sounds like a simple ldapmodify on a single server will suffice.

Thanks!

[Ludo]

Hi Scott,

You’re correct. Only one of the servers’ schema need to be updated over LDAP.

[Scott Heger]

Excellent. Thank you!

[Author]

Posts