[SERVER-16391] Ensure jstests are agnostic to primary election Created: 26/Nov/14  Updated: 11/Jul/16  Resolved: 03/Dec/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 2.8.0-rc2

Type: Bug Priority: Major - P3
Reporter: Ian Whalen (Inactive) Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-16420 More tests need to be agnostic to pri... Closed
Operating System: ALL
Participants:

 Description   

Only seen once:

LOGS

assert failed : conns[0] assumed to be master
Error: assert failed : conns[0] assumed to be master
    at Error (<anonymous>)
    at doassert (src/mongo/shell/assert.js:11:14)
    at assert (src/mongo/shell/assert.js:20:5)
    at C:\data\mci\shell\src\jstests\replsets\rollback.js:56:5
    at C:\data\mci\shell\src\jstests\replsets\rollback.js:134:2



 Comments   
Comment by Githook User [ 03/Dec/14 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-16391 fix minvalid2.js to be primary-agnostic
Branch: master
https://github.com/mongodb/mongo/commit/9268fd6df4027a79a19030f5f377eb88117a2025

Comment by Githook User [ 03/Dec/14 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-16391 archor primary in replset tests, or make agnostic to primary node
Branch: master
https://github.com/mongodb/mongo/commit/5598c216ca28234735999ca25b3f6f9a030f51e6

Comment by Eric Milkie [ 02/Dec/14 ]

There is no guarantee that a higher priority node will be elected first in a replica set. We will need to fix all jstests that assume this. Most of the tests can be fixed by prohibiting other nodes from standing for election, by assigning them a priority of 0.

Comment by Ian Whalen (Inactive) [ 01/Dec/14 ]

Saw a similar error message in rollback3.js:

http://buildlogs.mongodb.org/MCI_windows-64/builds/372141/test/replicasets_0/rollback3.js
https://mci.10gen.com/task_history/mongodb-mongo-master/replicasets?revision=ed023a2b488a74807334e8c0d3db57cf9552cf2c#/rollback3.js=fail

milkie what's the probability this is the same underlying problem?

Generated at Thu Feb 08 03:40:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.