[SERVER-20964] convert stepdown_killop.js to use fail point instead of bridging Created: 25/Aug/15 Updated: 25/Jan/17 Resolved: 16/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc1 |
| Type: | Improvement | Priority: | Minor - P4 |
| 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: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | RPL A (10/09/15), Repl B (10/30/15) | ||||||||
| Participants: | |||||||||
| Description |
|
On certain platforms, stepdown_killop.js fails while isolating the secondary node due to instability of the mongobridge tool on that platform. This test does not require the use of mongobridge. Replacing its use with a fail point that suspends oplog application will still allow us to test the desired functionality (killing a step down operation while the primary is waiting for secondaries to catch up) while making the test run a lot faster. ------ e07c554c6a OS X 10.8 DEBUG replicasets_WT (1st execution) https://logkeeper.mongodb.org/build/55db933d90413011a28aee7b/test/55dba4a490413011a28b6f6c
|
| Comments |
| Comment by Benety Goh [ 16/Oct/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
A similar enhancement was applied to stepdown_long_wait_time.js in | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Githook User [ 16/Oct/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Siyuan Zhou [ 15/Oct/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Reopening this ticket as this happened again on OS X 10.8 DEBUG. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Benety Goh [ 15/Oct/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Charlie Swanson [ 11/Sep/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Happened again here | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Jonathan Reams [ 27/Aug/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
This happened again here https://evergreen.mongodb.com/task/mongodb_mongo_master_osx_108_debug_replicasets_3765aa134fce806f3e146e870734922d75632e94_15_08_27_13_29_26 | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Benety Goh [ 26/Aug/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
stepdown_killop,js fails intermittently during the setup phase on certain platforms due to instability of the mongobridge tool. Bridging is not necessary for testing the desired functionality (killing an active step down operation). A fail point that suspends oplog application would work much better. 5d76623abc OS X 10.8 DEBUG replicasets_WT https://logkeeper.mongodb.org/build/55dd4dd2be07c47abf9365ab/test/55dd5fafbe07c47abf93832f
|