[SERVER-26220] Using stopOplogFetcher failpoint causes CPU looping Created: 21/Sep/16  Updated: 06/Dec/22  Resolved: 19/Oct/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.4.0-rc2

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Backlog - Replication Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-25702 add support to OplogFetcher for resta... Closed
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

See linked ticket for an example. It causes a new sync source to be chosen repeatedly, as long as the failpoint is on.



 Comments   
Comment by Githook User [ 19/Oct/16 ]

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}

Message: SERVER-26220 Using stopOplogFetcher failpoint causes CPU looping
Branch: master
https://github.com/mongodb/mongo/commit/e342912532c5cd106340b233eca5e49f9d69f0ab

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