You can take any number between 000 and 999, but every number can be used only once. I do it like this

replication of cn=config is stating with 00 replication of object-db of my provider is starting with 10 replication of object-db of my consumers is starting with 20

So it's easy look for a special replication in the log.

Am 04.03.25 um 10:16 schrieb Windl, Ulrich:

Stefan

Probably I was not quite clear enough: If I replicate cn=config to two servers, and I replicate the main DIT to (the same) two servers also, is it OK to assign one rid for each server, or do I need different rid for each? In my case I was using rid 5 and 6 for each of the two servers (independent from which item I replicated). But I wondered whether I should use something like rid 51, 52, 61, 62 instead, so that each replication has a unique RID.

Kind regards, Ulrich Windl

...

-----Original Message----- From: Stefan Kania stefan@kania-online.de Sent: Tuesday, March 4, 2025 9:29 AM To: openldap-technical@openldap.org Subject: [EXT] Re: Q: Uniqueness of syncrepl rid

Hi Uli,

the rid must be unique only on the server it self, you can uses the same rid on any of your LDAP-Server.

Stefan

Am 04.03.25 um 07:25 schrieb Windl, Ulrich:

...

Hi!

I have a question on the uniqueness of rid in syncrepl:

Do they have to be globally unique, or just unique within a database (olcDatabase config)?

Kind regards,

Ulrich Windl

On 04Mar25 08:29+0000, Marc wrote:

I think so. I can remember messing with a docker container so when it would be deployed it would generate a syncrepl id related to the current ip.

If I may define 'current ip' here:

AFAIK, the rid number space must be unique per slapd server (database syncrepl context). What I want to say is, if you syncreplicate from more than one upstream syncrepl-providers, they require distinct rid numbers. Thus, the 'current ip' would refer to the remote IP not the one of the server. Maybe this clear though :)