-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Query Execution
-
Fully Compatible
-
QE 2025-10-27
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Consider a long-running multi-delete operation that ends past the end of the logfile that we have (e.g. it ran for 24 hours on an active multi-TB collection). There would be no way to determine whether this op is running without analyzing db.currentOp() (which is not an easy task). And you also would need to know to look there.
A good option would be to log all long-running operations periodically, let's say each 10 minutes or so.
- is depended on by
-
SERVER-112568 Write a readme file about slow query logs
-
- Blocked
-
- is duplicated by
-
SERVER-111052 Log long-running in-progress operations
-
- Closed
-
- related to
-
SERVER-107414 A flavor of $currentOp to report long running operations
-
- Open
-
-
SERVER-112571 Consider moving Slow Query logs to a separate component
-
- Backlog
-
-
SERVER-112619 Enable slow in progress query logs by default
-
- In Progress
-
-
SERVER-111052 Log long-running in-progress operations
-
- Closed
-
-
SERVER-112493 Remove stdx::thread workaround from ttl unit tests
-
- Closed
-
-
SERVER-33880 Log currentOp information to mongod log during successful or attempted shutdown
-
- Backlog
-
-
SERVER-112606 Log long running operations on mongos
-
- Needs Verification
-