Hello,
I'm running a Cluster of 4 Servers of openldap-2.6.1
ServerID 1 ldaps://member1.example/ ServerID 2 ldaps://member2.example/ ServerID 3 ldaps://member3.example/ ServerID 4 ldaps://member4.example/ syncrepl rid=1 provider=ldaps://member1.example/ syncrepl rid=2 provider=ldaps://member2.example/ syncrepl rid=3 provider=ldaps://member3.example/ syncrepl rid=4 provider=ldaps://member4.example/ multiprovider on
the servers 1 and 2 are offline since a week or so. Now I like to remove servers 1 and 2 finally to fall back to a cluster of two members. The new config will look this way:
ServerID 1 ldaps://member3.example/ ServerID 1 ldaps://member4.example/ syncrepl rid=1 provider=ldaps://member3.example/ syncrepl rid=2 provider=ldaps://member4.example/ multiprovider on
Is this change of ID numbers a potential source of trouble?
Andreas
--On Friday, May 13, 2022 3:13 PM +0200 "A. Schulze" sca@andreasschulze.de wrote:
Hello,
I'm running a Cluster of 4 Servers of openldap-2.6.1
ServerID 1 ldaps://member1.example/ ServerID 2 ldaps://member2.example/ ServerID 3 ldaps://member3.example/ ServerID 4 ldaps://member4.example/ syncrepl rid=1 provider=ldaps://member1.example/ syncrepl rid=2 provider=ldaps://member2.example/ syncrepl rid=3 provider=ldaps://member3.example/ syncrepl rid=4 provider=ldaps://member4.example/ multiprovider on
the servers 1 and 2 are offline since a week or so. Now I like to remove servers 1 and 2 finally to fall back to a cluster of two members. The new config will look this way:
ServerID 1 ldaps://member3.example/ ServerID 1 ldaps://member4.example/ syncrepl rid=1 provider=ldaps://member3.example/ syncrepl rid=2 provider=ldaps://member4.example/ multiprovider on
Is this change of ID numbers a potential source of trouble?
The only problem I see here is that you have the same serverID for both nodes, and serverIDs are what must be unique across MMR servers. Not clear to me why you don't just drop SIDs 1 & 2 and keep 3 & 4 like you already have.
--Quanah
Quanah Gibson-Mount:
Hi Quanah!
The only problem I see here is that you have the same serverID for both nodes, and serverIDs are what must be unique across MMR servers.
this was a typo while writing the message, sorry.
Not clear to me why you don't just drop SIDs 1 & 2 and keep 3 & 4 like you already have.
it's only one of multiple instance of such a MMR cluster. All other use 1+2 to so this cluster should also do.
Andreas
--On Friday, May 13, 2022 7:07 PM +0200 "A. Schulze" sca@andreasschulze.de wrote:
Quanah Gibson-Mount:
Hi Quanah!
The only problem I see here is that you have the same serverID for both nodes, and serverIDs are what must be unique across MMR servers.
this was a typo while writing the message, sorry.
Not clear to me why you don't just drop SIDs 1 & 2 and keep 3 & 4 like you already have.
it's only one of multiple instance of such a MMR cluster. All other use 1+2 to so this cluster should also do.
So generally OpenLDAP won't care then. I would clean up the database references to the old SID values and out of the contextCSNs at some point, if you know how to do that properly, but it's not a huge deal.
--Quanah
openldap-technical@openldap.org
-
A. Schulze -
Quanah Gibson-Mount