Extends timeout maxTransactionLockRequestTimeoutMillis in Azure Cosmos DB for MongoDB

Question

Extends timeout maxTransactionLockRequestTimeoutMillis in Azure Cosmos DB for MongoDB

Pandhu Wibowo 0

Hi

We are facing interuption because of this maxTransactionLockRequestTimeoutMillis was set 5 seconds by default. How to modify or extends the timeout to be 30 seconds?

Thank you

Manasa Akula 250 Reputation points Microsoft External Staff

2025-04-22T05:01:33.55+00:00
Hi Pandhu Wibowo,

To modify the maxTransactionLockRequestTimeoutMillis setting to extend the timeout to 30 seconds, you can follow these steps:

Edit the MongoDB Configuration File:

Locate your MongoDB configuration file (mongod.conf).

Add or modify the setParameter section to include maxTransactionLockRequestTimeoutMillis with the desired timeout value (30000 milliseconds for 30 seconds).

setParameter: maxTransactionLockRequestTimeoutMillis: 30000

2.Restart MongoDB:

After making the changes, restart your MongoDB instance to apply the new configuration.

3.Verify the Setting:

You can verify that the setting has been applied correctly by connecting to your MongoDB instance and running the following command in the MongoDB shell:

db.adminCommand ({getParameter:1, maxTransactionLockRequestTimeoutMillis: 1 })

This should return the current value of maxTransactionLockRequestTimeoutMillis, confirming that it has been set to 30000 milliseconds (30 seconds).

please refer the doc for MongoDB Documentation

I hope this information helps. Please do let us know if you have any further queries.

If the comment is helpful, please click "Upvote it".
Pandhu Wibowo 0 Reputation points

2025-04-22T05:27:05.91+00:00

Hi @Manasa Akula

Thanks for your response. Is it suitable in Azure Cosmos DB for MongoDB?
Pandhu Wibowo 0 Reputation points

2025-04-22T05:27:27.53+00:00

And applicable for this one?
Manasa Akula 250 Reputation points Microsoft External Staff

2025-04-22T08:20:34.67+00:00

Hi Pandhu Wibowo

Please check the private message and let us know if you have any further queries.
Manasa Akula 250 Reputation points Microsoft External Staff

2025-04-23T00:41:42.3466667+00:00

Hi Pandhu Wibowo,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Manasa Akula 250 Reputation points Microsoft External Staff

2025-04-23T09:29:40.48+00:00
Hi @Pandhu Wibowo

In Azure Cosmos DB for MongoDB API, the maxTransactionLockRequestTimeoutMillis setting is fixed at 5 seconds for multi-document transactions. This timeout is not configurable, and there is currently no method to extend it to 30 seconds or any other value.

While we cannot modify the lock acquisition timeout, you can mitigate the impact of this limitation by:Optimizing Transaction Scope:

Limit the number of documents involved in a transaction to reduce lock contention.

Copy

Ensure that the operations within the transaction are as efficient as possible.

Implementing Retry Logic:

Incorporate retry mechanisms in your application to handle transient failures due to lock timeouts.

Use exponential backoff strategies to avoid overwhelming the system with retries.

Monitoring and Scaling:

Monitor your Cosmos DB account's throughput and adjust the Request Units (RUs) as needed to handle higher loads.

Consider scaling your Cosmos DB resources to accommodate more intensive workloads. Please refer the below doc https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/vcore/limits I hope this information helps. Please do let us know if you have any further queries. If the comment is helpful, please click "Upvote it".
Manasa Akula 250 Reputation points Microsoft External Staff

2025-04-24T00:42:48.76+00:00

Hi Pandhu Wibowo,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Your answer

Manasa Akula 250 Reputation points Microsoft External Staff

2025-04-22T05:01:33.55+00:00

Hi Pandhu Wibowo,

To modify the maxTransactionLockRequestTimeoutMillis setting to extend the timeout to 30 seconds, you can follow these steps:

Edit the MongoDB Configuration File:

Locate your MongoDB configuration file (mongod.conf).

Add or modify the setParameter section to include maxTransactionLockRequestTimeoutMillis with the desired timeout value (30000 milliseconds for 30 seconds).

setParameter: maxTransactionLockRequestTimeoutMillis: 30000

2.Restart MongoDB:

After making the changes, restart your MongoDB instance to apply the new configuration.

3.Verify the Setting:

You can verify that the setting has been applied correctly by connecting to your MongoDB instance and running the following command in the MongoDB shell:

db.adminCommand ({getParameter:1, maxTransactionLockRequestTimeoutMillis: 1 })

This should return the current value of maxTransactionLockRequestTimeoutMillis, confirming that it has been set to 30000 milliseconds (30 seconds).

please refer the doc for MongoDB Documentation

I hope this information helps. Please do let us know if you have any further queries.

If the comment is helpful, please click "Upvote it".
Pandhu Wibowo 0 Reputation points

2025-04-22T05:27:05.91+00:00

Hi @Manasa Akula

Thanks for your response. Is it suitable in Azure Cosmos DB for MongoDB?
Pandhu Wibowo 0 Reputation points

2025-04-22T05:27:27.53+00:00

And applicable for this one?
Manasa Akula 250 Reputation points Microsoft External Staff

2025-04-22T08:20:34.67+00:00

Hi Pandhu Wibowo

Please check the private message and let us know if you have any further queries.
Manasa Akula 250 Reputation points Microsoft External Staff

2025-04-23T00:41:42.3466667+00:00

Hi Pandhu Wibowo,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Manasa Akula 250 Reputation points Microsoft External Staff

2025-04-23T09:29:40.48+00:00

Hi @Pandhu Wibowo

In Azure Cosmos DB for MongoDB API, the maxTransactionLockRequestTimeoutMillis setting is fixed at 5 seconds for multi-document transactions. This timeout is not configurable, and there is currently no method to extend it to 30 seconds or any other value.

While we cannot modify the lock acquisition timeout, you can mitigate the impact of this limitation by:Optimizing Transaction Scope:

Limit the number of documents involved in a transaction to reduce lock contention.

Copy

Ensure that the operations within the transaction are as efficient as possible.

Implementing Retry Logic:

Incorporate retry mechanisms in your application to handle transient failures due to lock timeouts.

Use exponential backoff strategies to avoid overwhelming the system with retries.

Monitoring and Scaling:

Monitor your Cosmos DB account's throughput and adjust the Request Units (RUs) as needed to handle higher loads.

Consider scaling your Cosmos DB resources to accommodate more intensive workloads. Please refer the below doc https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/vcore/limits I hope this information helps. Please do let us know if you have any further queries. If the comment is helpful, please click "Upvote it".
Manasa Akula 250 Reputation points Microsoft External Staff

2025-04-24T00:42:48.76+00:00

Hi Pandhu Wibowo,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Share via

Extends timeout maxTransactionLockRequestTimeoutMillis in Azure Cosmos DB for MongoDB

Your answer