Runbook

MongoDB lock escalation conflicts.

Back to Runbooks

Overview

This incident type refers to situations where MongoDB database experiences lock escalation conflicts. MongoDB uses locks to control concurrent access to the database. When the number of locks held by a process reaches a certain threshold, the process may escalate its locks to a higher level, which can cause conflicts with other processes. These conflicts can result in performance degradation and even system crashes. Resolving this incident requires identifying the root cause of the lock escalation conflicts and implementing appropriate measures such as optimizing database queries, increasing the available system resources, or adjusting the MongoDB lock settings.

Parameters

Debug

Check if MongoDB is running

Check if MongoDB is stuck or unresponsive

Check if there are any lock escalations

Check if there are any active transactions

Check if there are any blocked transactions

Check the MongoDB log for any errors or warnings

Repair

Increase the number of available connections to the MongoDB server and optimize the queries to reduce contention and reduce the likelihood of lock escalation conflicts.

Configure MongoDB to use lock escalation sparingly or disable it altogether if it is causing too many conflicts.

Learn more

Related Runbooks

Check out these related runbooks to help you debug and resolve similar issues.