[SERVER-67258] ShardNotFound PM-2290 poc Created: 14/Jun/22  Updated: 06/Sep/22  Resolved: 06/Sep/22

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

Type: Bug Priority: Major - P3
Reporter: Andrew Witten (Inactive) Assignee: Andrew Witten (Inactive)
Resolution: Won't Do Votes: 0
Labels: sharding-nyc-subteam2-catalog-poc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-67128 Pre-populate ShardRegistry during sta... Closed
Operating System: ALL
Sprint: Sharding 2022-06-27, Sharding 2022-07-11, Sharding 2022-07-25, Sharding 2022-08-08, Sharding 2022-08-22, Sharding 2022-09-05, Sharding 2022-09-19
Participants:

 Description   

We are seeing error 

[js_test:commands_that_write_accept_wc_configRS] 	"errmsg" : "could not get updated shard list from config server :: caused by :: No shard found for host: ip-10-122-6-248:20021",[js_test:commands_that_write_accept_wc_configRS] 	"code" : 70,[js_test:commands_that_write_accept_wc_configRS] 	"codeName" : "ShardNotFound" 

in many tests.  Some relevant logs can be found [here|https://evergreen.mongodb.com/lobster/build/527dd273360214a54b4a88aa66faee62/test/62a22781245806611b222528#f~=100~ShardNotF&f~=100~ReadConcernMajorityNot.

One thing that I noticed is that we are seeing ReadConcernMajorityNotAvailable errors such as this:

"Error running periodic reload of shard registry","attr":{"error":"ReadConcernMajorityNotAvailableYet: could not get updated shard list from config server 

which may be causing these shardnotfound errors.


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