[SERVER-20590] slavedelay1.js - increase awaitReplication() time after adding a node Created: 21/Sep/15  Updated: 08/Aug/16  Resolved: 23/Sep/15

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 3.1.9

Type: Bug Priority: Major - P3
Reporter: Samantha Ritter (Inactive) Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-25486 increase wait time in slavedelay1.js ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: RPL A (10/09/15)
Participants:
Linked BF Score: 0

 Description   

https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_windows_64_replicasets_WT_ese_6c3e5661ecc19e4a95e6b776bdb7866739a49689_15_09_20_14_29_18

Test fails assert.soon because members are not ready, logs are filled with primary reporting an info message about syncing:

[js_test:slavedelay1] 2015-09-20T16:30:19.220+0000 		{
[js_test:slavedelay1] 2015-09-20T16:30:19.220+0000 			"_id" : 0,
[js_test:slavedelay1] 2015-09-20T16:30:19.220+0000 			"name" : "WIN-MIAKGV0GBFF:20010",
[js_test:slavedelay1] 2015-09-20T16:30:19.220+0000 			"health" : 1,
[js_test:slavedelay1] 2015-09-20T16:30:19.220+0000 			"state" : 1,
[js_test:slavedelay1] 2015-09-20T16:30:19.220+0000 			"stateStr" : "PRIMARY",
[js_test:slavedelay1] 2015-09-20T16:30:19.220+0000 			"uptime" : 9,
[js_test:slavedelay1] 2015-09-20T16:30:19.220+0000 			"optime" : Timestamp(1442766615, 1),
[js_test:slavedelay1] 2015-09-20T16:30:19.220+0000 			"optimeDate" : ISODate("2015-09-20T16:30:15Z"),
[js_test:slavedelay1] 2015-09-20T16:30:19.220+0000 			"infoMessage" : "could not find member to sync from",
[js_test:slavedelay1] 2015-09-20T16:30:19.220+0000 			"electionTime" : Timestamp(1442766614, 1),
[js_test:slavedelay1] 2015-09-20T16:30:19.220+0000 			"electionDate" : ISODate("2015-09-20T16:30:14Z"),
[js_test:slavedelay1] 2015-09-20T16:30:19.220+0000 			"configVersion" : 1,
[js_test:slavedelay1] 2015-09-20T16:30:19.220+0000 			"self" : true
[js_test:slavedelay1] 2015-09-20T16:30:19.220+0000 		}



 Comments   
Comment by Githook User [ 23/Sep/15 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-20590 increase awaitReplication() time after adding a node in replsets/slavedelay1.js
Branch: master
https://github.com/mongodb/mongo/commit/41a9ac6e4d5a0300ca8d136d5acbec5c003eaac6

Comment by Matt Dannenberg [ 23/Sep/15 ]

At this point in the test, a new node (with slaveDelay 30) has just been added to replica set and we awaitReplication() to allow it to catch up. As there is no evidence of any node dying or anything else, I think the syncing is just taking longer than we allow for.

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