[
https://issues.apache.org/jira/browse/CASSANDRA-18184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yong Jiang updated CASSANDRA-18184:
-----------------------------------
Attachment: 18184-trunk.txt
> 'Maximum memory usage reached' chunk cache log message doesn't specify which
> cache is exhausted
> -----------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-18184
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18184
> Project: Cassandra
> Issue Type: Bug
> Components: Observability/Logging
> Reporter: Brad Schoening
> Assignee: Yong Jiang
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 4.x
>
> Attachments: 18184-trunk.txt
>
>
> With Cassandra 4.0.x, we are seeing this cassandra.log message very
> frequently on the majority of our Cassandra 4.0 clusters:
> _[INFO ] [epollEventLoopGroup-5-3] cluster_id=99 ip_address=127.0.0.50
> NoSpamLogger.java:92 - Maximum memory usage reached (128.000MiB), cannot
> allocate chunk of 8.000MiB_
> It took me several weeks to track down what it means, until I saw this
> start-up message
> _BufferPools.java:49 - Global buffer pool limit is 2.000GiB for
> chunk-cache and 128.000MiB for networking_
> This maximum memory usage warning would benefit from clarifying that its the
> {*}network cache{*}, not the *off-heap chunk* *cache* which is exhausted.
> With 'chunk cache' in both warning messages, they're too easily confused.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
