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

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

"After investigating the server setup, there are a few problems here.
The new server was being configured with sid=001 which was already
assigned to the original master. That's clearly going to screw things

On Mon, 2017-03-06 at 10:03 -0800, Quanah Gibson-Mount wrote:
> --On Monday, March 06, 2017 5:24 PM +0000 mberg@synacor.com wrote:
> > Reading back over the report on ITS-8281, the reported behavior
> > would have been a collision of generating a new contextCSN as well
> > as duplicating the producer's SID.  So it's generated contextCSN
> > would have masked the one it never committed from the original
> > master.
> I'm not sure what you mean by duplicating the producer's SID.  Both
> nodes 
> had unique SID values.  There were no duplicated SIDs.
> --Quanah
> --
> Quanah Gibson-Mount
> Product Architect
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by
> OpenLDAP:
> <http://www.symas.com>
Matthew Berg <mberg@synacor.com>
This message and any attachment may contain information that is confidential and/or proprietary. Any use, disclosure, copying, storing, or distribution of this e-mail or any attached file by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please notify the sender by reply email and delete the message and any attachments. Thank you.