[ https://issues.apache.org/jira/browse/CASSANDRA-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Miklosovic updated CASSANDRA-19022: ------------------------------------------ Fix Version/s: 5.1 (was: 5.x) Since Version: NA Source Control Link: https://github.com/apache/cassandra/commit/009146959afccc67adbae24e59a7ba38930fea87 Resolution: Fixed Status: Resolved (was: Ready to Commit) > Fix nodetool gcstats output, support human-readable units and various formats > ----------------------------------------------------------------------------- > > Key: CASSANDRA-19022 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19022 > Project: Apache Cassandra > Issue Type: Bug > Components: Tool/nodetool > Reporter: Brad Schoening > Assignee: Ling Mao > Priority: Normal > Fix For: 5.1 > > Time Spent: 50m > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org