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-M3
- PM-234-T-oplog-fetch

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Sharding 2021-01-25
Linked BF Score:
0
Story Points:
1
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

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

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

Created:: Jan 09 2021 06:41:00 PM UTC
Updated:: Oct 29 2023 09:58:59 PM UTC
Resolved:: Jan 12 2021 12:43:24 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates