Script #97
mongodb
Monitoringread-onlyMin Version: 4.0MongoDB Transaction Stats and Write Conflicts
Shows open and aborted transaction counts. Reveals long transaction and conflict problems.
#transactions#serverStatus#write-conflict
mongodb · javascript
const s = db.serverStatus();
({
transactions: s.transactions,
global_lock: s.globalLock.currentQueue,
wt_concurrent: s.wiredTiger.concurrentTransactions
});Operational Notes & Remediation Guidance
High write conflicts in WiredTiger indicate document contention from concurrent writes to the same document or index key.
Production Safety & Execution Standards
- This script is designed for read-only diagnostics; it does not alter schema or modify data directly.
- Prior to executing on production systems under high load, verify the target database version (Min. Version: 4.0).
- Exercise caution with mutating actions (e.g., terminating sessions or dropping indexes) referenced in the notes section.
Other MONGODB Diagnostic Scripts
View All (100)#81Performance
Find Long-Running Operations in MongoDB (currentOp)
Lists active operations running longer than 5 seconds with plan summary and lock-wait info. Helps pick the operation to kill during a slowdown.
View Script
#82Storage
MongoDB Collection and Index Sizes
Ranks collections by document count, data, storage and index size. Used for capacity planning and spotting bloated indexes.
View Script
#83Performance
Find Unused Indexes in MongoDB ($indexStats)
Lists never-used indexes per collection. Offers cleanup candidates to cut write cost and memory use.
View Script
#84Replication
MongoDB Replica Set Lag and Oplog Window
Shows member state, lag behind the primary and the oplog window. Monitors replication health and resync risk.
View Script