Info
Attached test. Observation based on test:
1. If replSetReconfig contains
{ priority: 0 }
, test passes.
2. In the failure case, the primary does not relinquish it's primary status.
3. Test runs fine in 2.4.6 & 2.5.2.
Top User Comments
auto commented on Mon, 30 Sep 2013 19:08:09 +0000:
Author:
{u'username': u'dannenberg', u'name': u'Matt Dannenberg', u'email': u'matt.dannenberg@10gen.com'}
Message: SERVER-10823 fix buildbot breakage
setOtherPrimary() asserts that we are not the primary
msgCheckState() was making sure the node isn't primary before calling setOtherPrimary()
but it was comparing members instead of just member ids
due to recent changes to reconfig (by which, a reconfig may not reset all connections and cause an election on tag changes), there is a race condition with the members
but the member id should be consistant and safe
Branch: master
https://github.com/mongodb/mongo/commit/043238005510c70d2d59a6228c58f0f44685d143
auto commented on Tue, 24 Sep 2013 19:07:48 +0000:
Author:
{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}
Message: SERVER-10823 update member configs properly on tags-only reconfigs
fixes problems caused by SERVER-6376
Branch: master
https://github.com/mongodb/mongo/commit/0be5ade7cdccccaef2f11b31819fd671c7476c71
mattd@10gen.com commented on Fri, 20 Sep 2013 19:53:43 +0000:
This is my fault (caused by how I fixed SERVER-6376). I am working on a fix.
