[
https://issues.apache.org/jira/browse/CASSANDRA-21474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18108757#comment-18108757
]
Stefan Miklosovic edited comment on CASSANDRA-21474 at 8/27/26 9:49 AM:
------------------------------------------------------------------------
For the record, we changed custom executor for ImmediateExecutor which resolved
all above-mentioned issues.
trunk https://pre-ci.cassandra.apache.org/job/cassandra/691/
6.0 https://pre-ci.cassandra.apache.org/job/cassandra-6.0/135/
was (Author: smiklosovic):
trunk https://pre-ci.cassandra.apache.org/job/cassandra/691/
6.0 https://pre-ci.cassandra.apache.org/job/cassandra-6.0/135/
> NoSpamLogger uses unbounded cache that could lead to memory exhaustion
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-21474
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21474
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Observability/Logging
> Reporter: Kathiresan Selvaraj
> Assignee: Viktoriia Kotovets
> Priority: Normal
> Fix For: 7.x, 6.x
>
> Attachments: ci_summary.html, results_details.tar.xz
>
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> The {{NoSpamLogger}} class maintains an unbounded cache of log statement keys
> without any eviction policy, which poses a memory leak risk.
> * Unbounded cache growth: The {{lastMessage}} map in {{NoSpamLogger.java}}
> uses a {{NonBlockingHashMap}} with no size limit or eviction policy.
> * When log messages contain dynamic content (e.g., query strings in
> tombstone warnings), each unique message creates a new cache entry.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
