[ https://issues.apache.org/jira/browse/CASSANDRA-18400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-18400: ----------------------------------------- Mentor: Brandon Williams > Nodetool info should report on the new networking cache > ------------------------------------------------------- > > Key: CASSANDRA-18400 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18400 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool > Reporter: Brad Schoening > Assignee: Ningzi Zhan > Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.x > > > CASSANDRA-15229 separated the chunk and network cache, creating a new > network_cache_size parameter. > However, *nodetool info* does not report the in-use size of this cache or a > hit ratio as it does for key, row, counter and chunk cache. > {quote}Exceptions : 4 > Key Cache : entries 2852, size 297.59 KiB, capacity 100 MiB, 2406561 hits, > 2409424 requests, 0.999 recent hit rate, 14400 save period in seconds > Row Cache : entries 0, size 0 bytes, capacity 0 bytes, 0 hits, 0 requests, > NaN recent hit rate, 0 save period in seconds > Counter Cache : entries 0, size 0 bytes, capacity 50 MiB, 0 hits, 0 requests, > NaN recent hit rate, 7200 save period in seconds > Chunk Cache : entries 1118, size 55.02 MiB, capacity 992 MiB, 4695794 misses, > 7179421 requests, 0.346 recent hit rate, 24.145 microseconds miss latency > Percent Repaired : 0.0% > {quote} > However, when its full, it will be logged: > {quote}[INFO ] [epollEventLoopGroup-5-12] cluster_id=1 ip_address=127.1.1.1 > NoSpamLogger.java:92 - Maximum memory usage reached (128.000MiB), cannot > allocate chunk of 8.000MiB > {quote} > -- 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