[SERVER-20761] stepdown_long_wait_time.js fails intermittently with "waiting for state indicator" Created: 02/Oct/15  Updated: 25/Jan/17  Resolved: 06/Oct/15

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

Type: Bug Priority: Major - P3
Reporter: J Rassi Assignee: Benety Goh
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   

The test should be waiting for the primary to step down separately from waiting for the secondary to start a new election to succeed the primary.


Two failures of stepdown_long_wait_time.js observed in replicasets_auth suite on Enterprise Windows today. The test failure mode is that an election is expected to succeed in 30 seconds; the election does not succeed.

Failed tasks:

Excerpt from first failure above:

[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 assert.soon failed, msg:waiting for state indicator state for 30000ms
[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 doassert@src/mongo/shell/assert.js:15:14
[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 assert.soon@src/mongo/shell/assert.js:194:13
[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 ReplSetTest.prototype.waitForIndicator@src/mongo/shell/replsettest.js:1063:1
[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 ReplSetTest.prototype.waitForState@src/mongo/shell/replsettest.js:1020:5
[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 @jstests\replsets\stepdown_long_wait_time.js:76:5
[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 @jstests\replsets\stepdown_long_wait_time.js:10:2
[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 
[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 2015-10-02T15:44:33.365+0000 E QUERY    [thread1] Error: assert.soon failed, msg:waiting for state indicator state for 30000ms :
[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 doassert@src/mongo/shell/assert.js:15:14
[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 assert.soon@src/mongo/shell/assert.js:194:13
[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 ReplSetTest.prototype.waitForIndicator@src/mongo/shell/replsettest.js:1063:1
[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 ReplSetTest.prototype.waitForState@src/mongo/shell/replsettest.js:1020:5
[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 @jstests\replsets\stepdown_long_wait_time.js:76:5
[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 @jstests\replsets\stepdown_long_wait_time.js:10:2
[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 
[js_test:stepdown_long_wait_time] 2015-10-02T15:44:33.365+0000 failed to load: jstests\replsets\stepdown_long_wait_time.js



 Comments   
Comment by Githook User [ 06/Oct/15 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-20761 clean up stepdown_long_wait_time.js - wait for old primary to step down completely before checking for new primary
Branch: master
https://github.com/mongodb/mongo/commit/0eb5debef127afff66aeee15426261b877f276ff

Comment by Benety Goh [ 05/Oct/15 ]

466f05960f OS X 10.8 replicasets_WT

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

https://logkeeper.mongodb.org/build/560e90d390413021b1b394b2/test/560ea47cbe07c4135fb52303

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