[SERVER-72884] Remove usages of non causally consistent ShardRegistry::getShardForHostNoReload accessor Created: 16/Jan/23  Updated: 26/Oct/23

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Tommaso Tocci Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 1
Labels: oldshardingemea, shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-50206 Remove "NoReload" ShardRegistry looku... Blocked
Duplicate
duplicates SERVER-35790 Add shardId information to RemoteComm... Closed
Assigned Teams:
Catalog and Routing
Participants:
Story Points: 3

 Description   

This is the last standing non causally consistent accessor left in the ShardRegistry.

Is currently used by ShardingTaskExecutor and in ShardingNetworkConnectionHook during response processing.


Generated at Thu Feb 08 06:23:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.