[SERVER-23046] Reimplement operation pipelining applier work before updating-position/reporting Created: 10/Mar/16  Updated: 06/Dec/22  Resolved: 14/Jun/19

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

Type: Improvement Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-21237 ReplSetTest.prototype.awaitReplicatio... Closed
is depended on by SERVER-21107 Improve protocol version 1 replicatio... Closed
Related
related to SERVER-21129 Allow pipelining of applier work befo... Closed
Assigned Teams:
Replication
Sprint: Repl C (11/20/15)
Participants:

 Description   

Currently the applier must (sequentially) do the following in a loop:

  1. batch oplog entries
  2. apply and record in local oplog
  3. journal, including minvalid
  4. report/update-position

The task here is to break the last two steps (journal + reporting) into a separate process which doesn't block the next batch from starting/applying. This should allow higher throughput on the replicas without adversely affecting latency.


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