How to configure Mongodb server parameters like wiredTigerConcurrentReadTransactions and wiredTigerConcurrentWriteTransactions in MonGoDb Atlas version?
What is the default value of these parameters in Atlas? Can we increase the count by increasing the cluster tier?
We have big number of concurrent read/write transactions. Seems like some transactions are aborting. May be related to above parameters default count.
Hi @Basil_Abraham,
Welcome to the MongoDB community forum!
Unfortunately you will not be able to directly configure the wiredTigerConcurrentReadTransactions and wiredTigerConcurrentWriteTransactions parameters as setParameter is one of the unsupported commands in Atlas.
However, if you have a dedicated Atlas cluster (M10+) it may be possible to tune some parameters for your use case:
Please contact Atlas support if your use case requires access to a command not currently supported by the existing Atlas database user privileges.
If you do choose to contact support, I would recommend providing further information regarding the issues you are attempting to address with the configuration of those parameters as they may provide alternate suggestions based on your use case or cluster metrics.
Hope this helps,
Jason
Hi @ Jason_Tran, Thanks for your reply.
Did below parameter do the job for parameters wiredTigerConcurrentReadTransactions and `wiredTigerConcurrentWriteTransactions in atlas ?
Hi @Basil_Abraham,
Did below parameter do the job for parameters wiredTigerConcurrentReadTransactions and `wiredTigerConcurrentWriteTransactions in atlas ?
The Connection Limits for Atlas Clusters are from the net.maxIncomingConnections configuration option. Attempting to change wiredTigerConcurrentReadTransactions and wiredTigerConcurrentWriteTransactions server parameters won’t increase the Atlas connection limit. You’ll need to select the cluster tier that matches the connection limit requirement for your application(s).
Hope this helps!
Jason
