Loading...

XML

Word

Printable

JSON

Details

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.2.18, 3.4.11, 3.6.0-rc1
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Completed:

3.2.18, 3.4.11
Sprint:
Repl 2017-10-23

Description

The ReplBatcher has been identified as an actor that keeps a long-running OperationContext. This can cause problems such as WT table drops to fail until the OperationContext is destroyed.

https://github.com/mongodb/mongo/blob/8210549ab754524b155ea45eb6675d717873cb21/src/mongo/db/repl/sync_tail.cpp#L753

Attachments

Issue Links

is related to

SERVER-22766 Dynamic oplog sizing for WiredTiger nodes

Closed

SERVER-31654 ReplBatcher should recalculate batch limits after oplog is resized via replSetResizeOplog

Backlog

related to

SERVER-31101 WT table not dropped after collection is dropped due to long-running OperationContext

Closed

Activity

People

Assignee:: Benety Goh

Reporter:: Daniel Gottlieb (Inactive)

Participants:: Benety Goh, Daniel Gottlieb, Githook User

Votes:: 0 Vote for this issue

Watchers:: 7 Start watching this issue

Dates

Created:: Oct 16 2017 06:40:01 PM UTC

Updated:: Oct 30 2023 11:12:44 PM UTC

Resolved:: Oct 20 2017 02:11:07 PM UTC