Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.9.0
Affects Version/s: None
Component/s: Sharding
Labels:
- PM-234-M2
- PM-234-T-oplog-fetch

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Sharding 2020-11-30
Linked BF Score:
0
Confidence Status:
None
Work Order:
3

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

mutablebson::Document::getObject() renders a full copy of the updated document. This can be expensive for larger documents. At minimum we should skip calling it when the collection isn't even sharded like UpdateStage::checkUpdateChangesShardKeyFields() does. Better would be to consolidate some the _doc.getObject() calls that UpdateStage::checkUpdateChangesShardKeyFields(), UpdateStage::wasReshardingKeyUpdated(), and updates which weren't performed in-place all do.

is caused by

SERVER-49825 Replicate updates changing value under new shard key pattern as delete + insert in a transaction

Closed

related to

SERVER-54040 Resharding may fail to throw WouldChangeOwningShard despite destined recipient having changed

Closed

SERVER-57666 Convert getDestinedRecipient() in resharding_util to be a class method

Closed

SERVER-58918 Replace getDestinedRecipient() in the code-base with calls into the ReshardingDonorWriteRouter object

Closed

Assignee:: Max Hirschhorn
Reporter:: Max Hirschhorn
Participants:: Githook User, Max Hirschhorn
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: Nov 20 2020 07:08:58 PM UTC
Updated:: Oct 29 2023 10:00:12 PM UTC
Resolved:: Nov 21 2020 03:47:14 AM UTC
Confidence Status Last Update:: 20/Nov/20 7:42 PM