[SERVER-49820] Allow setting destined recipient in oplog entries Created: 23/Jul/20  Updated: 29/Oct/23  Resolved: 03/Aug/20

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

Type: New Feature Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: PM-234-M2, PM-234-T-oplog-fetch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done before SERVER-49822 Add destined recipient to oplog entri... Closed
has to be done before SERVER-49823 Add destined recipient to oplog entri... Closed
has to be done before SERVER-49824 Add destined recipient to oplog entri... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-08-10
Participants:

 Description   

The "reshardDest" field should be added to the DurableReplOperation struct.

{
    op: 'i' | 'u' | 'd',
    ns: "<database>.<collection>", ui: <existingUUID>,
    reshardDest: "<recipientShardId>",
    o: { ... }, ...
}

And the destined recipient should be added as a parameter to OplogEntry::OplogEntry() and makeOplogEntryDoc(). Consider using boost::optional<ShardId> here and the shard_id type in oplog_entry.idl.



 Comments   
Comment by Githook User [ 03/Aug/20 ]

Author:

{'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}

Message: SERVER-49820 Allow setting destined recipient in oplog entries
Branch: master
https://github.com/mongodb/mongo/commit/8336a2ebf2b4b255e09ce3ec29d2baad7fa8c5e4

Generated at Thu Feb 08 05:20:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.