[SERVER-28184] remove election_timing.js (and lib/election_timing_test.js) Created: 03/Mar/17  Updated: 05/Apr/17  Resolved: 03/Mar/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.2.13, 3.4.4, 3.5.4

Type: Bug Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-26410 Rewrite election_timing.js as a perf ... Backlog
is related to SERVER-26142 disable timing checks in election_tim... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Repl 2017-03-06
Participants:
Linked BF Score: 0

 Description   

Since disabling the timing checks in SERVER-26142, election_timing.js is reduced to a series of test cases that trigger elections by stepping down or stopping the primary under various election configurations (protocol version 0 or 1).

A typical election_timing.js test run typically takes longer than 10 minutes which is a little excessive compared to existing replica set tests.

This makes election_timing.js redundant with existing C++ unit tests and JS tests in jstests/replsets.



 Comments   
Comment by Githook User [ 30/Mar/17 ]

Author:

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

Message: SERVER-28184 removed election_timing.js

Also removed jstests/libs/election_timing_test.js

Since disabling the timing checks in SERVER-26142, election_timing.js is
reduced to a series of test cases that trigger elections by stepping
down or stopping the primary under various election configurations
(protocol version 0 or 1).

A typical election_timing.js test run typically takes longer than 10
minutes which is a little excessive compared to existing replica set tests.

This makes election_timing.js redundant with existing C++ unit tests and JS
tests in jstests/replsets.

(cherry picked from commit 30b80c79081ff98b513c6c61e9dbae82242689ae)
Branch: v3.2
https://github.com/mongodb/mongo/commit/a586a2713a148d388c21520e18c174e463631183

Comment by Githook User [ 30/Mar/17 ]

Author:

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

Message: SERVER-28184 removed election_timing.js

Also removed jstests/libs/election_timing_test.js

Since disabling the timing checks in SERVER-26142, election_timing.js is
reduced to a series of test cases that trigger elections by stepping
down or stopping the primary under various election configurations
(protocol version 0 or 1).

A typical election_timing.js test run typically takes longer than 10
minutes which is a little excessive compared to existing replica set tests.

This makes election_timing.js redundant with existing C++ unit tests and JS
tests in jstests/replsets.

(cherry picked from commit 30b80c79081ff98b513c6c61e9dbae82242689ae)
Branch: v3.4
https://github.com/mongodb/mongo/commit/2a89b6019718d6e978e16dc683ad85919de61bf5

Comment by Githook User [ 03/Mar/17 ]

Author:

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

Message: SERVER-28184 removed election_timing.js

Also removed jstests/libs/election_timing_test.js

Since disabling the timing checks in SERVER-26142, election_timing.js is
reduced to a series of test cases that trigger elections by stepping
down or stopping the primary under various election configurations
(protocol version 0 or 1).

A typical election_timing.js test run typically takes longer than 10
minutes which is a little excessive compared to existing replica set tests.

This makes election_timing.js redundant with existing C++ unit tests and JS
tests in jstests/replsets.
Branch: master
https://github.com/mongodb/mongo/commit/30b80c79081ff98b513c6c61e9dbae82242689ae

Generated at Thu Feb 08 04:17:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.