[SERVER-28096] Fix 3.2 jstest stepUp functions Created: 24/Feb/17  Updated: 06/Dec/17  Resolved: 14/Apr/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.2.12
Fix Version/s: 3.2.13

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2017-04-17
Participants:
Linked BF Score: 0

 Description   

These stepUp functions appear in:
write_concern_after_stepdown.js
read_committed_stale_history.js
double_rollback.js
double_rollback_early.js
rollback_with_socket_error_steady_state.js
write_concern_after_stepdown_and_stepup.js.

These all try to accomplish the same thing but have different implementations. There should be one stepUp function that makes sure all nodes are electable after it returns. https://github.com/mongodb/mongo/commit/3823a20f0186d0e6b544212fb423f9f0ef786235 contains an example of how this can look.

Alternatively, we could backport SERVER-20844 to 3.2 to make this unnecessary.



 Comments   
Comment by Githook User [ 14/Apr/17 ]

Author:

{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}

Message: SERVER-28096 fix jstest stepUp functions
Branch: v3.2
https://github.com/mongodb/mongo/commit/f98bd7d1a376ab741024d21e20e4b1b48d9a0af6

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