You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brad Schoening (Jira)" <ji...@apache.org> on 2024/08/15 19:32:00 UTC
[jira] (CASSANDRA-19022) Nodetool gcstats correctly displays Direct Memory usage and supports printing in table format
[ https://issues.apache.org/jira/browse/CASSANDRA-19022 ]
Brad Schoening deleted comment on CASSANDRA-19022:
--------------------------------------------
was (Author: bschoeni):
[~maoling] is this ready for review? It wasn't in patch submitted status.
> Nodetool gcstats correctly displays Direct Memory usage and supports printing in table format
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-19022
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19022
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/nodetool
> Reporter: Brad Schoening
> Assignee: Ling Mao
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If {{io.netty.maxDirectMemory}} is not specified, Netty defaults the limit to the max heap size. Thus, direct memory in use can be significant.
> However, trying this on two different platform and the result returned in gcstats is always -1:
> {noformat}
> Interval (ms) Max GC Elapsed (ms)Total GC Elapsed (ms)Stdev GC Elapsed (ms) GC Reclaimed (MB) Collections Direct Memory Bytes
> 2792770717 274 665186 54 41276288089024 6120 -1{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org