SERVER-136787Investigating
Streamable ReplicaSetMonitor accumulates hundreds-thousands of concurrent awaitable hello streams per target after NetworkInterfaceExceededTimeLimit, leading to OOM on arbiters / data nodes
h3. Environment * MongoDB Community 8.0.30 (Debian 12 based image, `mongod --version` gitVersion 360770fbc9b6a893748150d2ab2799e119b9fac9, tcmalloc-google) * Sharded cluster on Kubernetes (StatefulSets, hosts addressed through a headless Service DNS name) ** CSRS: 3 members ** 2 shards, each PSA (primary + secondary + arbiter) ** 2 mongos * HDD storage, resource-constrained dev cluster (arbiter memory limit 1Gi, CSRS 2Gi, data 8Gi) * Same image/topology in a second (production) cluster shows the