[SERVER-61003] ReadConcernMajorityNotAvailableYet errors from ShardRegistry must be retried Created: 26/Oct/21  Updated: 29/Oct/23  Resolved: 17/Dec/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.3.0, 5.1.2, 5.0.6, 5.2.0-rc3

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Problem/Incident
causes SERVER-62386 Coverity analysis defect 121298: Pars... Closed
Related
related to SERVER-60916 CPS Restores failed with a snapshot w... Closed
related to SERVER-62163 Complete TODO listed in SERVER-61003 Closed
related to SERVER-67896 Remove uncessary ShardRegistry reload... Closed
is related to SERVER-57280 ShardRegistry must be initialized bef... Closed
is related to SERVER-57519 Make ARS use causally consistent Shar... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.2, v5.1, v5.0, v4.4
Sprint: Sharding EMEA 2021-11-15, Sharding EMEA 2021-11-29, Sharding EMEA 2021-12-13, Sharding EMEA 2021-12-27
Participants:
Linked BF Score: 46

 Description   

ShardRegistry::reload() must never fail with ReadConcernMajorityNotAvailableYet but rather retry reading from the config server.

The retries should happen with exponential backoff capped to 30 seconds, in order to don't overwhelm the CSRS but - at the same - not retry after too long.



 Comments   
Comment by Githook User [ 24/Dec/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-61003 ReadConcernMajorityNotAvailableYet errors from ShardRegistry must be retried
Branch: v5.1
https://github.com/mongodb/mongo/commit/7d07aed4f54220c572071dbc32cff8b70de52e54

Comment by Githook User [ 24/Dec/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-61003 ReadConcernMajorityNotAvailableYet errors from ShardRegistry must be retried
Branch: v5.2
https://github.com/mongodb/mongo/commit/43d15218d9b05dfac3120428aea9394f8487557e

Comment by Githook User [ 23/Dec/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-61003 ReadConcernMajorityNotAvailableYet errors from ShardRegistry must be retried
Branch: v5.0
https://github.com/mongodb/mongo/commit/ae1292b93bac1075faeacb6b015a8eefb1623b72

Comment by Githook User [ 17/Dec/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-62163 Complete TODO listed in SERVER-61003
Branch: master
https://github.com/mongodb/mongo/commit/85cd2f089103402615f1dc214d5606b0191760ff

Comment by Githook User [ 17/Dec/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-61003 ReadConcernMajorityNotAvailableYet errors from ShardRegistry must be retried
Branch: master
https://github.com/mongodb/mongo/commit/f086caabba92a63a81403db4e139441d39a80451

Generated at Thu Feb 08 05:51:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.