Details
-
Improvement
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
4.0.10, 4.1.2, 5.0-alpha1, 5.0
-
None
-
Operability
-
Normal
-
All
-
None
-
Description
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.
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%
However, when its full, it will be logged:
[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
It should report a line similar to the above:
Network Cache : entries ?, size ? MiB, capacity ? MiB, ? misses, ? requests, ? recent hit rate
Also, not sure why the above show NaN for row and counter cache, is there is a divide by zero error when the entries are zero?