[SERVER-27323] Use stopOplogFetcher failpoint instead of rsSyncApplyStop failpoint in write_concern_after_stepdown_and_stepup.js Created: 07/Dec/16  Updated: 05/Apr/17  Resolved: 19/Dec/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.4.2, 3.5.2

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

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.4, v3.2
Sprint: Platforms 2017-01-23
Participants:
Linked BF Score: 0

 Description   

rsSyncApplyStop does not stop replication, it just stops applying buffered oplog entries. stopOplogFetcher actually stops replication



 Comments   
Comment by Githook User [ 03/Jan/17 ]

Author:

{u'username': u'spencerjackson', u'name': u'Spencer Jackson', u'email': u'spencer.jackson@mongodb.com'}

Message: SERVER-27323: Use stopOplogFetcher failpoint in write_concern_after_stepdown_and_stepup.js

(cherry picked from commit e4f7522828c0514e57ffdbcf82505598fa8fc741)
Branch: v3.4
https://github.com/mongodb/mongo/commit/e12eca2fcb14714800e899bfcd91d7f0225aebde

Comment by Githook User [ 19/Dec/16 ]

Author:

{u'username': u'spencerjackson', u'name': u'Spencer Jackson', u'email': u'spencer.jackson@mongodb.com'}

Message: SERVER-27323: Use stopOplogFetcher failpoint in write_concern_after_stepdown_and_stepup.js
Branch: master
https://github.com/mongodb/mongo/commit/0cac996da9aa66bf50a34eebaf08a1ca5b31cf9b

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