15 May
2017
15 May
'17
3:05 p.m.
From: Quanah Gibson-Mount Sent: Thursday, April 20, 2017 1:26 PM
It's fine for there to be legacy entryCSNs and a contextCSN for serverID
of
- However, it is not fine for any master in an MMR setup to have a
specific serverID of 0. If you're running with serverID's 0-3, I'd simply try an ldapmodify on the server with 0 to set its serverID to 4, and then do a modification against it, so it generates a new contextCSN that gets pushed out to all nodes.
I went ahead and updated the serverID from 0 to 4 when I dropped in the patched binary, it seems to have gone smoothly. I'm planning to migrate the memberOf configuration over the summer to the dynamic list implementation, which is going to require a dump to ldif and reload, I'll go ahead and strip out the legacy serverid 0 contextCSN's then.
Thanks.