How can MongoDB 4.0.12 be configured to SLOW its rate of re-connecting to its replica members when they are down?

I had MongoDB replica members die. The online replica members get “connection refused” when trying down members, then re-attempt to connect as fast as the CPU and network allow. This crushes the CPU and makes the log files grow huge as Mongo retries it’s connection hundreds of time ps per minute.

I'd rather MongoDB retry to reach replica members only once per minute, rather than immediately after getting a failure. There’s no reason to retry a down server hundreds of times per minute.

Is there a way to configure MongoDB to wait for some seconds before attempting a reconnect when a replica member is down? I can't find any such setting in the server & replica settings.

How can MongoDB 4.0.12 be configured to SLOW its rate of re-connecting to its replica members when they are down?

I had MongoDB replica members die. The online replica members get “connection refused” when trying down members, then re-attempt to connect as fast as the CPU and network allow. This crushes the CPU and makes the log files grow huge as Mongo retries it’s connection hundreds of time ps per minute.

I'd rather MongoDB retry to reach replica members only once per minute, rather than immediately after getting a failure. There’s no reason to retry a down server hundreds of times per minute.

Is there a way to configure MongoDB to wait for some seconds before attempting a reconnect when a replica member is down? I can't find any such setting in the server & replica settings, and this seems like it would be an important thing to set.

How can MongoDB 4.0.12 be configured to SLOW its rate of re-connecting to its replica members when they are down?

I had MongoDB replica members die. The online replica members get “connection refused” then re-attempt to connect as fast as the CPU and network allow. This crushes the CPU and makes the mongo log grow huge as Mongo retries it’s connection hundreds of time ps per minute.

I'd rather MongoDB retry to reach replica members only once per minute, rather than immediately after getting a failure.

Is there a way to configure MongoDB to wait for some seconds before attempting a reconnect when a replica member is down? I can't find any such setting in the config settings.

How can MongoDB 4.0.12 be configured to SLOW its rate of re-connecting to its replica members when they are down?

I had MongoDB replica members die. The online replica members get “connection refused” when trying down members, then re-attempt to connect as fast as the CPU and network allow. This crushes the CPU and makes the log files grow huge as Mongo retries it’s connection hundreds of time ps per minute.

I'd rather MongoDB retry to reach replica members only once per minute, rather than immediately after getting a failure. There’s no reason to retry a down server hundreds of times per minute.

Is there a way to configure MongoDB to wait for some seconds before attempting a reconnect when a replica member is down? I can't find any such setting in the server & replica settings.