SERVER-137718Open

max_time_ms_mongos_deadline.js counts config server connections as shard connection churn

h2. Problem {{jstests/noPassthrough/network/max_time_ms_mongos_deadline.js}} asserts that mongos creates no new egress connections while a find hits MaxTimeMSExpired on the shard. Its helper {{getShardHostPoolStats()}} sums {{connPoolStats.hosts}} over every host, including the config server replica set members. Shortly after startup, mongos issues config reads with nearest read preference. When such a read lands on a config node that has no pooled connection yet, mongos opens a new connec

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification
auto-reverted