-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Query Optimization
-
Fully Compatible
-
v8.0, v7.0
-
QO 2024-08-05, QO 2024-08-19
-
200
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
The work SERVER-90282 makes it so that when a tassert() failure occurs during a find command, the command that was running at the time of failure is logged. We should extend this mechanism to also log other basic facts about the operation, in particular those that are available from CurOp and OpDebug.
I think CurOp / OpDebug is probably small enough that we don't have to worry about logging these extra diagnostics on every tassert failure (in case there is a bug that causes the tassert rate to spike).
- is related to
-
SERVER-90282 Add more diagnostics to tassert failures
-
- Closed
-
- related to
-
SERVER-91686 Improve mongod's signal handler to print out current thread's command object
-
- Closed
-
-
SERVER-105731 Consider enabling new diagnostic logs for failing commands
-
- Open
-
-
SERVER-105732 Consider enabling new diagnostic logs for failing commands
-
- Open
-
-
SERVER-105727 Consider enabling new diagnostic logs for failing commands
-
- Backlog
-
-
SERVER-105728 Consider enabling new diagnostic logs for failing commands
-
- Backlog
-
-
SERVER-105730 Consider enabling new diagnostic logs for failing commands
-
- Backlog
-
-
SERVER-105734 Consider enabling new diagnostic logs for failing commands
-
- Backlog
-
-
SERVER-92767 Extend diagnostic logging on tassert failure to apply to additional commands
-
- Closed
-
-
SERVER-105733 Consider enabling new diagnostic logs for failing commands
-
- Closed
-
-
SERVER-105729 Consider enabling new diagnostic logs for failing commands
-
- Needs Scheduling
-