Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.8.0
Affects Version/s: None
Component/s: Replication, Sharding
Labels:
- PM-234-M2
- PM-234-T-oplog-fetch

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2020-09-21, Sharding 2020-10-05
Linked BF Score:
0
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

Call MutableOplogEntry::setReshardDest() with the result of getDestinedRecipient() in MutableOplogEntry::makeInsertOperation(). (for transactions)
Call MutableOplogEntry::setReshardDest() with the result of getDestinedRecipient() in repl::logInsertOps(). (for non-transactions)

causes

SERVER-53678 No-op for filling in destined recipient for insert oplog entries adds overhead on non-shardsvrs

Closed

SERVER-53679 No-op for filling in destined recipient for insert oplog entries adds overhead on shardsvrs not running resharding

Closed

has to be done after

SERVER-49820 Allow setting destined recipient in oplog entries

Closed

SERVER-49821 Define utility function for getting recipient which would own document under new shard key

Closed

related to

SERVER-75787 remove std::function reference from repl::logInsertOps

Closed

Assignee:: Alexander Taskov (Inactive)
Reporter:: Max Hirschhorn
Participants:: Alexander Taskov, Githook User, Max Hirschhorn
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jul 23 2020 02:55:06 AM UTC
Updated:: Oct 29 2023 10:05:22 PM UTC
Resolved:: Sep 30 2020 12:41:07 AM UTC