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 2025/11/20 18:06:00 UTC

[jira] [Updated] (CASSANDRA-21037) Backport fix to nodetool gcstats output

     [ https://issues.apache.org/jira/browse/CASSANDRA-21037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brad Schoening updated CASSANDRA-21037:
---------------------------------------
    Source Control Link:   (was: https://github.com/apache/cassandra/commit/009146959afccc67adbae24e59a7ba38930fea87)

> Backport fix to nodetool gcstats output
> ---------------------------------------
>
>                 Key: CASSANDRA-21037
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21037
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Tool/nodetool
>            Reporter: Brad Schoening
>            Priority: Normal
>             Fix For: 5.0.x
>
>
> 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