[
https://issues.apache.org/jira/browse/CASSANDRA-21474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18103355#comment-18103355
]
Stefan Miklosovic edited comment on CASSANDRA-21474 at 8/10/26 11:38 AM:
-------------------------------------------------------------------------
[~viktoriiakotovets] thank you for the patch, I commented on the PR, once
addressed we need to have another +1 from a committer before we merge.
was (Author: smiklosovic):
[~viktoriiakotovets] thank you for the patch, I commented on the PR, once
addressed we need to have another +1 for a committer before we merge.
> 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: 6.x, 7.x
>
> Time Spent: 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]
