[SERVER-20589] auth_slaveok_routing.js fails waiting for client to recognize hosts Created: 14/Sep/15  Updated: 07/Oct/15  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: Charlie Swanson Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: RPL A (10/09/15)
Participants:

 Description   

Task
Logs

[js_test:auth_slaveok_routing] 2015-09-12T04:34:02.982-0400 assert.soon failed, msg:timed out waiting for replica set client to recognize hosts
[js_test:auth_slaveok_routing] 2015-09-12T04:34:02.982-0400 doassert@src/mongo/shell/assert.js:15:14
[js_test:auth_slaveok_routing] 2015-09-12T04:34:02.982-0400 assert.soon@src/mongo/shell/assert.js:194:13
[js_test:auth_slaveok_routing] 2015-09-12T04:34:02.982-0400 ReplSetTest.awaitRSClientHosts@src/mongo/shell/replsettest.js:323:1
[js_test:auth_slaveok_routing] 2015-09-12T04:34:02.982-0400 ReplSetTest.awaitRSClientHosts@src/mongo/shell/replsettest.js:309:13
[js_test:auth_slaveok_routing] 2015-09-12T04:34:02.982-0400 @jstests/sharding/auth_slaveok_routing.js:88:1



 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-20589 increase oplogSize in sharding/auth_slaveok_routing.js to decrease flakiness
Branch: master
https://github.com/mongodb/mongo/commit/73dbf7ffcdfe54a93510920a2ad3873bcd97c67d

Comment by Matt Dannenberg [ 14/Sep/15 ]

The replica set shard seems to have two nodes enter rollback when we do not expect them to, due to falling off the back of the oplog of the node elected primary. As a result, the nodes are not secondaries as awaitRSClientHosts expects. If we see this again, we may want to consider increasing the oplog size.

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