[SERVER-67912] Reduce set of non-causally consistent API of the ShardRegistry Created: 08/Jul/22  Updated: 29/Oct/23  Resolved: 11/Jul/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: None
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
Gantt Dependency
has to be done after SERVER-67901 Stop gossiping lastCommittedOpTime in... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-07-11, Sharding EMEA 2022-07-25
Participants:

 Description   

This is a step forward to SERVER-50206.
In this ticket the following ShardRegistry function will be removed in favor of their causally consistent counterpart:

  • ShardRegistry::getShardNoReload()
  • ShardRegistry::getNumShardsNoReload()
  • ShardRegistry::getAllShardIdsNoReload()


 Comments   
Comment by Githook User [ 11/Jul/22 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-67912 Reduce set of non-causally consistent API of the ShardRegistry
Branch: master
https://github.com/mongodb/mongo/commit/b36b3fa21d50a41242efb1ad8d0739739e99dd5c

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