Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.9.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-10-05, Sharding 2020-10-19
Confidence Status:
None
Work Order:
3

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

Add a decoration on OperationContext (similar to documentKeyDecoration) for the destined recipient.
Emplace the decoration with the result of getDestinedRecipient() in OpObserverImpl::aboutToDelete().
Call MutableOplogEntry::setReshardDest() with the value emplaced in the decoration in MutableOplogEntry::makeDeleteOperation(). (for transactions)
Call MutableOplogEntry::setReshardDest() with the value emplaced in the decoration in replLogDelete(). (for non-transactions)

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

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:56:55 AM UTC
Updated:: Oct 29 2023 10:05:22 PM UTC
Resolved:: Oct 12 2020 03:45:52 PM UTC
Confidence Status Last Update:: 01/Oct/20 8:20 PM