-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: 8.2.0-rc0, 8.1.0
-
Component/s: None
-
Catalog and Routing
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
When launching any test in the sharding_jscore_passthrough suite, the config server always generates two traces with ERROR severity:
> truncate -s0 empty.js && buildscripts/resmoke.py run --suite=sharding_jscore_passthrough empty.js | grep '"s":"E"'
[j0:c:prim] {"t":{"$date":"2025-05-15T13:17:52.699+00:00"},"s":"E", "c":"SHARDING", "id":6791402, "svc":"S", "ctx":"UpdateReplicaSetOnConfigServer","msg":"Error updating replica set on config server. Couldn't find shard.","attr":{"replicaSetConnectionStr":"config-rs/localhost:20000"}}
[j0:c:prim] {"t":{"$date":"2025-05-15T13:17:55.458+00:00"},"s":"E", "c":"SHARDING", "id":7524000, "svc":"S", "ctx":"ShardingDDLCoordinator-1","msg":"Failed sharding DDL coordinator","attr":{"coordinatorId":{"namespace":"config.system.sessions","operationType":"createCollection_V4"},"reason":"IllegalOperation: There are no suitable shards to create the sessions collection on"}}
We should investigate if those are indicative of an actual issue, or rather they are acceptable and their log severity should be lowered.