-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Fully Compatible
-
ALL
-
Repl 2026-09-14
-
None
-
None
-
None
-
None
-
None
-
None
-
None
As seen in linked ticket, when a standby mongod is shutting down and is in quiesce mode, the ReplicaSetMonitor repeatedly spins and spams logs. In the listed case, mongod ended up spamming a 8 GB of logs in 10 minutes.
{"t":{"$date":"2026-08-21T17:22:26.074+00:00"},"s":"I", "c":"NETWORK", "id":4712102, "ctx":"NetworkInterfaceTL-ReplicaSetMonitor-TaskExecutor","msg":"Host failed in replica set","attr":{"replicaSet":"atlas-t0pa6p-shard-0","host":"atlas-t0pa6p-shard-00-01.pidno1.mongodb-qa.net:27017","error":{"code":91,"codeName":"ShutdownInProgress","errmsg":"The server is in quiesce mode and will shut down"},"action":{"dropConnections":false,"requestImmediateCheck":false,"outcome":{"host":"atlas-t0pa6p-shard-00-01.pidno1.mongodb-qa.net:27017","success":false,"errorMessage":"ShutdownInProgress: The server is in quiesce mode and will shut down","topologyVersion":{"processId":{"$oid":"6a870a915fc4ed28cc63f508"},"counter":3}}}}}
{"t":{"$date":"2026-08-21T17:22:26.074+00:00"},"s":"I", "c":"-", "id":4333222, "ctx":"NetworkInterfaceTL-ReplicaSetMonitor-TaskExecutor","msg":"RSM received error response","attr":{"host":"atlas-t0pa6p-shard-00-01.pidno1.mongodb-qa.net:27017","error":"ShutdownInProgress: The server is in quiesce mode and will shut down","replicaSet":"atlas-t0pa6p-shard-0","response":{"topologyVersion":{"processId":{"$oid":"6a870a915fc4ed28cc63f508"},"counter":3},"ok":0,"errmsg":"The server is in quiesce mode and will shut down","code":91,"codeName":"ShutdownInProgress","remainingQuiesceTimeMillis":14913,"$clusterTime":{"clusterTime":{"$timestamp":{"t":1787332944,"i":2184}}},"operationTime":{"$timestamp":{"t":1787326815,"i":2}}}}}
The reason we are spamming may be because we're in "expedited" mode.
{"t":{"$date":"2026-08-21T17:22:32.017+00:00"},"s":"I", "c":"-", "id":4333227, "ctx":"NetworkInterfaceTL-ReplicaSetMonitor-TaskExecutor","msg":"RSM monitoring host in expedited mode until we detect a primary","attr":{"host":"atlas-t0pa6p-shard-00-01.pidno1.mongodb-qa.net:27017","replicaSet":"atlas-t0pa6p-shard-0"}}
Some possible solutions:
1) throttle the logging, by using a time / count based suppressor, like this
2) change the log levels in a static way in the config
3) change the order we shut down components so the RSM is shut down first.
The line in the FTDC is roughly when queisce mode has ended and mongod is spamming logs from there on.
