[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#8607) Second master in MMR config logging contextCSN changes to accesslog

--On Thursday, March 02, 2017 10:36 PM +0000 mberg@synacor.com wrote:

> I'm not sure if there is any guard against writing an older contextCSN
> than is currently stored, but this could theoretically rewind the
> stored contextCSN on A if there is any latency in replication from B.

Older contextCSNs will be ignored.  And it is accurate to then have a 
contextCSN for each server in the system.  That was part of the initial 
problem in 8281.  I still see no evidence of incorrect behavior. ;)

--Quanah



--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>