A large number of threads and the maxIncomingConnections option

Hi!I am running a replicaset in an operator and faced with the following problem:
pmm-monitoring and top inside the running container show a large number of threads, about 30 thousand. Basically, these are network threads. I tried to limit them using the option maxIncomingConnections = 400. But it didn’t help. It seems to me, unfortunately, the maxIncomingConnections parameter was not passed to the mongod process.
Please tell me if the maxIncomingConnections parameter works in the operator and is it possible to reduce the number of threads in mongodb?

1 Like

I connect to the question. I have a similar problem.

2 Likes

It seems, I understood how to send options into mongod process. We should use configmaps, which keep mongod.conf with need options and another log and pid path. But I got another problems - if I decreased maxIncomingConnections, then mongod process used almost whole connections limit after a while. And I didn’t load db at this moment.

1 Like

I researched this problem and created new topic to continue the analysis.

1 Like