You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Francisco Guerrero (Jira)" <ji...@apache.org> on 2026/08/14 23:01:00 UTC
[jira] [Updated] (CASSANDRA-21578) Protect uncaught_exceptions virtual table against the crash path
[ https://issues.apache.org/jira/browse/CASSANDRA-21578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francisco Guerrero updated CASSANDRA-21578:
-------------------------------------------
Bug Category: Parent values: Availability(12983)Level 1 values: Process Crash(12992)
Complexity: Normal
Component/s: Virtual Tables
Discovered By: Code Inspection
Severity: Normal
Status: Open (was: Triage Needed)
> Protect uncaught_exceptions virtual table against the crash path
> ----------------------------------------------------------------
>
> Key: CASSANDRA-21578
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21578
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Virtual Tables
> Reporter: Francisco Guerrero
> Assignee: Francisco Guerrero
> Priority: Normal
>
> In CASSANDRA-20858, a virtual table was added to add the ability to query uncaught exceptions. However, this patch brought three issues that we are trying to address here:
> - Guard the persist(t) call so a throw can't skip inspectThrowable's disk_failure_policy / OOM die handling.
> - Drain preInitialisationBuffer under its monitor in flush() to avoid a ConcurrentModificationException that could abort node startup.
> - Bound preInitialisationBuffer so a startup exception storm (or a tool context that never flushes) can't retain stack traces without limit.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org