[SERVER-77209] Figure out our oplog replication story Created: 17/May/23  Updated: 15/Jun/23  Resolved: 15/Jun/23

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

Type: Task Priority: Major - P3
Reporter: Moustafa Maher Assignee: Huayu Ouyang
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-77803 Group HPDM oplog entries together whe... Closed
Sprint: Execution Team 2023-05-29, Execution Team 2023-06-12
Participants:

 Description   
  • Investigate and come up with proposals on how to do our Oplog replication plan for our cloning.
    We have two operations that are othrogonal to each other
  • Clone data
  • Clone index data

So we need to come up with a plan for :

  • Do you need to have a new oplog type, or we can use one of the existent ones ?
  • How the primary will batch these writes (data and index) ?
  • How the secondary will do on receiving oplog ?

Generated at Thu Feb 08 06:34:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.