[SERVER-22075] election_timing.js election timed out Created: 17/Dec/15  Updated: 23/Nov/16  Resolved: 06/Jan/16

Status: Closed
Project: Core Server
Component/s: Replication, Shell
Affects Version/s: None
Fix Version/s: 3.2.3, 3.3.0

Type: Bug Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: test-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-22080 add a fire and forget shutdown method... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Participants:
Linked BF Score: 0

 Description   

replicasets_WT failed on enterprise-rhel-62-64-bit

election_timing.js - Logs | History

BF Ticket Generated by siyuan.zhou



 Comments   
Comment by Githook User [ 14/Jan/16 ]

Author:

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

Message: SERVER-22075 disable flakey test case in election_timing.js

(cherry picked from commit aaf53b13854fde5271bb6e394295bd2ed6c56736)
Branch: v3.2
https://github.com/mongodb/mongo/commit/7779d7993383502db34363844264cbfc5cd67fa9

Comment by Githook User [ 06/Jan/16 ]

Author:

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

Message: SERVER-22075 disable flakey test case in election_timing.js
Branch: master
https://github.com/mongodb/mongo/commit/aaf53b13854fde5271bb6e394295bd2ed6c56736

Comment by Daniel Pasette (Inactive) [ 27/Dec/15 ]

Seeing this on both 3.2 and master. mostly osx, but also once on linux64. Do we need to disable this test as these seem spurious.

Comment by Matt Dannenberg [ 21/Dec/15 ]

Proposed solution: disable that test case until we have a fire and forget shutdown method inside the shell.

Comment by Matt Dannenberg [ 21/Dec/15 ]

This failure seems to be pretty consistently part of the testV1StopTimeout1500 run. Looking at the logs I see a new primary appear within the expected window. However, the test waits for the previous primary to be completely stopped before looking to see if a new primary stepped up. Since the election timeout window is so short here, the shutdown time can be greater than the expected election, causing the test to fail.

I know there were some recent bugs around shutdown, might this be related to those?
I don't know enough about the testing methodology to feel comfortable changing the jstests/lib/election_timing_test.js and this didn't a problem for the first month or so of this tests existence.

Comment by Adam Midvidy [ 18/Dec/15 ]

This is also failing on the 3.2 branch.

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