[
https://issues.apache.org/jira/browse/CASSANDRA-20858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18017512#comment-18017512
]
Dmitry Konstantinov edited comment on CASSANDRA-20858 at 9/1/25 4:38 PM:
-------------------------------------------------------------------------
As an option we can use Byteman for this purpose to inject an exception (if we
want to emulate an end-to-end case), there are several tests which use this
library to inject some faulty behaviour...
Another simpler option is to invoke
org.apache.cassandra.utils.JVMStabilityInspector#uncaughtException directly in
the test.
was (Author: dnk):
As an option we can use Byteman for this purpose to inject an exception, there
are several tests which use this library to inject some faulty behaviour...
Another simpler option is to invoke
org.apache.cassandra.utils.JVMStabilityInspector#uncaughtException directly in
the test.
> Add virtual table to expose last N uncaught exceptions
> ------------------------------------------------------
>
> Key: CASSANDRA-20858
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20858
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Virtual Tables
> Reporter: Paulo Motta
> Assignee: Stefan Miklosovic
> Priority: Normal
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> There's a metric {{StorageMetrics.uncaughtExceptions}} that tracks uncaught
> exception count.
> Let's add a {{system_views.exceptions}} table with the following information:
> * ExceptionClass
> * Count
> * Last Message
> * Last StackTrace
> * Last Occurence Time
> This will give more visibility into uncaught exceptions allowing operators to
> easily find unexpected issues that can be hidden in logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
