Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.6.6, 4.0.0-rc0
Affects Version/s: 3.4.14, 3.6.4, 3.7.9
Component/s: Replication
Labels:
None

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

v3.6, v3.4
Sprint:
Repl 2018-05-21
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Initial sync limits batches during oplog application to 5000 ops/dur::UncommittedBytesLimit (512 MB) while steady state replication has been limiting batches to 50,000 ops/100MB since commit b53a93270c8ea8ccc9f43a0cf0592353b0edd012 (~~SERVER-24242~~).

Getting the batch limits from SyncTail will also allow us to tweak the maximum number of operations in each batch during initial sync using the server parameter replBatchLimitOperations.

is related to

SERVER-36496 Cache pressure issues during oplog replay in initial sync

Closed

SERVER-32335 Update initial sync to use new Applier interface for oplog application

Closed

SERVER-35405 Change default setting for replBatchLimitOperations

Closed

related to

SERVER-34942 Stuck with cache full during oplog replay in initial sync

Closed

Assignee:: Benety Goh
Reporter:: Benety Goh
Participants:: Benety Goh, Githook User, Kelsey Schubert
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: May 08 2018 07:52:53 PM UTC
Updated:: Oct 29 2023 10:31:58 PM UTC
Resolved:: May 10 2018 03:10:26 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates