[SERVER-16376] get_last_error.js fails because it does not expect chaining to occur Created: 01/Dec/14  Updated: 04/Dec/14  Resolved: 02/Dec/14

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

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

Operating System: ALL
Participants:

 Description   

LOGS
TASK HISTORY

 m31000| 2014-12-01T15:40:05.444+0000 I QUERY    [conn1] command test.$cmd command: getLastError { getlasterror: 1.0, w: 3.0, wtimeout: 1000.0 } keyUpdates:0  reslen:231 1001ms
Trying w=3 with 2 nodes up, 1000ms timeout.
{
	"lastOp" : Timestamp(1417448404, 1),
	"connectionId" : 1,
	"n" : 0,
	"syncMillis" : 0,
	"waited" : 1001,
	"wtimeout" : true,
	"writtenTo" : [
		"ip-10-13-142-105:31000"
	],
	"err" : "timeout",
	"errmsg" : "timed out waiting for slaves",
	"code" : 64,
	"ok" : 1
}
assert: [1] != [2] are not equal : undefined
Error: [1] != [2] are not equal : undefined
    at Error (<anonymous>)
    at doassert (src/mongo/shell/assert.js:11:14)
    at Function.assert.eq (src/mongo/shell/assert.js:38:5)
    at /data/mci/shell/src/jstests/gle/get_last_error.js:62:8



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

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-16376 Make nodes in jstests/gle/get_last_error.js choose their sync source deterministically.

The test expects w:majority writes to happen faster than a heartbeat interval when a single
non-primary node fails. If, however, that failed node is the intermediate in a replication
chain, there can be a multi-second lag until the other nodes recognize the failure. Change
the test to disallow chaining, because it is not the subject of the test.
Branch: master
https://github.com/mongodb/mongo/commit/f51e0f461f903b1ecb014c7ad796374933e12c60

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