[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Fixing a multi-master divergence
- To: openldap-technical@openldap.org
- Subject: Fixing a multi-master divergence
- From: Guillaume Rousse <guillomovitch@gmail.com>
- Date: Mon, 03 Sep 2012 15:52:14 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=mE1tuRKqPZk3kQgMX+I15kchPfUB8qCxY27rcbYg4oU=; b=Z1PPU745Cwnae7HGBAdyTLFB5wbPhyPAvQJwVFIquaFkxY9A+6Wb5lY5DstdITiRbK yhwGVxBbK1Q6sW7srFe3qhlD/seiHsOJpnECCXqM0bqFq9fOcntb9FsCtm4FAhEHSw8d OrhNeajC+MBCiaideQ7WFaOYREPiGU+9LOs1dGIoTMoi/+gye6JP7PuyPcsaq3m+UpRr /Y0Lbsz1SQ4No6Qx5zFSIMfo1TbdlFK22yKtwHdxcARgDC+bY5TqX1jZHRe+sPpMui1u HJf5nRCzrqWwUfrQZaFUACEGgF3HoT5P5HlcjSHXhxsquEamhPwdk2jxF2wG0Nw+Du8V RgBg==
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120829 Thunderbird/15.0
Hello list.
I have two openldap servers 2.4.23 running in a multimaster setup whose
content diverged at some point. Fortunatly, I had different backup files
for both, which allowed to me to reconciliate content manually. I
reimported the resulting ldif file in one of the server, re-exported it
through slapcat, and reimported it in the other server, after dropping
all existing databases (including acceslog one).
However, I end up with two bases with multiple and divergent contextCSN
values:
contextCSN: 20120420144311.217351Z#000000#000#000000
contextCSN: 20120903132738.849382Z#000000#001#000000
contextCSN: 20120903132426.927826Z#000000#002#000000
contextCSN: 20120420144311.217351Z#000000#000#000000
contextCSN: 20120903132426.925966Z#000000#001#000000
contextCSN: 20120903132924.793560Z#000000#002#000000
Any attempt to manually reduce this to a single value in the backup file
before restoration ended in infinite refresh request from the second
servers and "stale cookie" error messages.
So, my questions are:
- is this an expectable state to have multiple values for contextCSN ?
- does it hurt, beyond making synchronisation checking almost impossible ?
- how to return to a stable situation ?
I can't change ldap version easily, and I'd rather return to classic
master-slave setup if the problem is not fixable otherwise.
--
BOFH excuse #213:
Change your language to Finnish.