-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
Sharding 2021-01-25
-
0
-
1
getDestinedRecipient() is called by OpObserverImpl for all write operations and returns boost::none when there isn't an ongoing resharding operation. Calling CollectionShardingState::get() and CollectionShardingState::getCollectionDescription() even when sharding isn't enabled adds overhead. ShardingState::enabled() can be used to detect whether the server was started with --shardsvr to avoid the performance regression for stand-alone mongods and replica sets.
- is caused by
-
SERVER-49822 Add destined recipient to oplog entries from inserts
- Closed
- related to
-
SERVER-53679 No-op for filling in destined recipient for insert oplog entries adds overhead on shardsvrs not running resharding
- 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