[email protected] wrote: > Hello, > > Under typical circumstances we run a config database and have a single > application database for ldap data. We run consumers replicating from > providers where they replicate the entire application database. We detect > delayed replication by querying consumer CSNs and comparing them to the > provider CSNs to determine if any consumers have delayed replication through > a health check script that executes every few minutes. > > For one particular use case we replicate a subset of the application > database, but our replication check cannot work for this use case. It appears > because we're not replicating the entire database we do not copy the provider > CSNs over to the consumers (which live at the base level, and we're copying a > DIT below that level) and therefore I cannot ask the consumers what their > 'latest csn' is since they do not seem to have one. > > Is there any recommended way I can check that the consumer replication is > functioning properly when replicating a subset of the provider database?
The consumer still tracks the provider's contextCSN and still stores it in the DIT's context entry. If you slapcat the consumer DB you'll see it. > > Thanks for the consideration. > Tom > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/
