Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: Logging, Write Ops
Labels:
- diagnosibility
- storch

Assigned Teams:

Query Execution
Backwards Compatibility:
Fully Compatible
Sprint:
QE 2025-10-27
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
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

(4 related to)

Assignee:: Ivan Fefer
Reporter:: Alexander Komyagin (Inactive)
Participants:: Alexander Komyagin, Bruce Lucas, Eric Sedor, Githook User, Ivan Fefer, Scott Hernandez
Votes:: 23 Vote for this issue
Watchers:: 43 Start watching this issue

Created:: Apr 08 2015 08:47:38 PM UTC
Updated:: Oct 23 2025 02:43:29 PM UTC
Resolved:: Oct 23 2025 09:53:47 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates