[SERVER-26220] Using stopOplogFetcher failpoint causes CPU looping - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 3.4.0-rc2
Component/s: Replication
Labels:
None

Assigned Teams:

Replication
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
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.

Attachments

Issue Links

related to

SERVER-25702 add support to OplogFetcher for restarting oplog query

Closed

Activity

People

Assignee:: Backlog - Replication Team

Reporter:: Eric Milkie

Participants:: Backlog - Replication Team, Eric Milkie, Githook User

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: Sep 21 2016 05:42:57 PM UTC

Updated:: Dec 06 2022 04:16:14 AM UTC

Resolved:: Oct 19 2016 08:04:13 PM UTC