# A large number of threads and the maxIncomingConnections option

**URL:** <https://forums.percona.com/t/a-large-number-of-threads-and-the-maxincomingconnections-option/12571>\
**Category:** Percona Operator for MongoDB\
**Tags:** percona, mongodb\
**Created:** [October 13, 2021, 2:27pm UTC](https://forums.percona.com/t/a-large-number-of-threads-and-the-maxincomingconnections-option/12571 "2021-10-13T14:27:40Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![nikita.savchenko](https://avatars.discourse-cdn.com/v4/letter/n/7feea3/32.png) [@nikita.savchenko](https://forums.percona.com/u/nikita.savchenko)\
**Post date:** [October 16, 2021, 5:02pm UTC](https://forums.percona.com/t/a-large-number-of-threads-and-the-maxincomingconnections-option/12571/3 "2021-10-16T17:02:51Z")

</div>

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.

---

_[View the full topic](https://forums.percona.com/t/a-large-number-of-threads-and-the-maxincomingconnections-option/12571)._