-
Type:
Bug
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
ALL
-
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
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.
- depends on
-
SERVER-67128 Pre-populate ShardRegistry during startup at Config shard
-
- Closed
-