--On Thursday, April 20, 2017 11:34 PM +0200 Michael Ströder michael@stroeder.com wrote:
quanah@symas.com wrote:
It's fine for there to be legacy entryCSNs and a contextCSN for serverID of 0. However, it is not fine for any master in an MMR setup to have a specific serverID of 0.
Would it be possible to check serverID during slapd startup with MMR setup and fail to start with an error message in case serverID is 0?
Perhaps a failure if someone tries to set olcMirrorMode to TRUE when serverID is 0. That covers the MMR case, but it doesn't cover the non-MMR case where unique serverIDs are required with separate masters and glued databases.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
Quanah Gibson-Mount wrote:
--On Thursday, April 20, 2017 11:34 PM +0200 Michael Ströder michael@stroeder.com wrote:
quanah@symas.com wrote:
It's fine for there to be legacy entryCSNs and a contextCSN for serverID of 0. However, it is not fine for any master in an MMR setup to have a specific serverID of 0.
Would it be possible to check serverID during slapd startup with MMR setup and fail to start with an error message in case serverID is 0?
Perhaps a failure if someone tries to set olcMirrorMode to TRUE when serverID is 0.
That covers the MMR case, but it doesn't cover the non-MMR case where unique serverIDs are required with separate masters and glued databases.
Catching the MMR case would already be a real improvement.
The latter case is far less common and people glueing DBs are likely more familiar with OpenLDAP setups.
Ciao, Michael.
-
Michael Ströder -
Quanah Gibson-Mount