OpenLDAP
Up to top level
Build   Contrib   Development   Documentation   Historical   Incoming   Software Bugs   Software Enhancements   Web  

Logged in as guest

Viewing Incoming/8790
Full headers

From: quanah@openldap.org
Subject: N-Way MMR w/o serverID in at least one entry causes REFRESH
Compose comment
Download message
State:
0 replies:
0 followups:

Major security issue: yes  no

Notes:

Notification:


Date: Tue, 12 Dec 2017 01:15:13 +0000
From: quanah@openldap.org
To: openldap-its@OpenLDAP.org
Subject: N-Way MMR w/o serverID in at least one entry causes REFRESH
Full_Name: Quanah Gibson-Mount
Version: 2.4.45
OS: N/A
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (47.208.148.239)


If one has configured N-WAY MMR in such a fashion that only one master ever gets
the write ops (whether this is mirrormode or other methodologies), and there are
zero entries in the database with an entryCSN of the other masters in the
system, attempts to bring those other masters back up will result in a REFRESH
phase on those masters, and potentially destabilize the entire cluster (See
ITS#8789 for example).

To avoid this, we should document that best practice involves having one object
per master that is only ever modified by that master, so there is always a
minimum of one object in the database with a CSN matching that master.  This
should avoid the REFRESH issue when bringing up a failed master.
Up to top level
Build   Contrib   Development   Documentation   Historical   Incoming   Software Bugs   Software Enhancements   Web  

Logged in as guest


The OpenLDAP Issue Tracking System uses a hacked version of JitterBug

______________
© Copyright 2013, OpenLDAP Foundation, info@OpenLDAP.org