[SERVER-67896] Remove uncessary ShardRegistry reload retry logic Created: 08/Jul/22  Updated: 29/Oct/23  Resolved: 13/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:
Related
is related to SERVER-61003 ReadConcernMajorityNotAvailableYet er... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-07-11, Sharding EMEA 2022-07-25
Participants:

 Description   

In SERVER-61003 we added a logic on the ShardRegistry reload function to retry ReadConcernMajorityNotAvailableYet error coming from the CSRS.

Retrying this error shouldn't be necessary at all since this errors could only happen during initialization of the ShardRegistry and before the sharding state is marked as initialized.



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

Author:

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

Message: SERVER-67896 Remove uncessary ShardRegistry reload retry logic
Branch: master
https://github.com/mongodb/mongo/commit/9e9eb5bf0b0d457bee144e7e90bfd8e3bf75c798

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