preWarmConnectionPool() is ran during the mongos main startup, and it is ultimately a best-effort. However, failures when reading the list of shards from the configsvr will cause preWarmConnectionPool to fail, which results in mongos exiting with an error code 5 (ExitCode::shardingError)
Similarly to SERVER-62036, we should also make failures on preWarmConnectionPool() not end the process
- is caused by
-
SERVER-44152 Pre-warm connection pools in mongos
-
- Closed
-
- is related to
-
SERVER-106321 Catalog client's getAllShards should throw on failure always rather than sometimes returning a status
-
- Closed
-
- related to
-
-
- Closed
-