[Date Prev][Date Next]
----- "Pierangelo Masarati" <firstname.lastname@example.org> wrote:
> andylockran wrote:
> > In the third box of code, this appears to set up the Master node
> with 3
> > serverIDs +URLS, when previously it was set up with a single
> > (which I assumed to be its identifier) is this correct?
> The serverID config statement (olcServerID attribute in back-config)
> used to inform a specific server about its own id within a local
> replication pool. Without URL, only one occurrence of serverID is
> allowed. When the URL is specified, multiple occurrences are allowed,
> but only one takes effect: the one whose URL matches the listener of
> server. So the URL-qualified multiple occurrences of serverID
> allow to share the same configuration within multiple servers of the
> same replication pool, guaranteeing that each server will pick up the
> correct id based on the URL.
Maybe this should be added to the replication section of the admin guide.
The man page is consise:
serverID <integer> [<URL>]
Specify an integer ID from 0 to 4095 for this server (limited to 3 hexadecimal digits). These IDs are required
when using multimaster replication and each master must have a unique ID. Note that this requirement also applies
to separate masters contributing to a glued set of databases. If the URL is provided, this directive may be
specified multiple times, providing a complete list of participating servers and their IDs. The fully qualified
hostname of each server should be used in the supplied URLs. The IDs are used in the "replica id" field of all
CSNs generated by the specified server. The default value is zero. Example:
OpenLDAP Engineering Team.
Community developed LDAP software.