[
https://issues.apache.org/jira/browse/CASSANDRA-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18023852#comment-18023852
]
Brad Schoening commented on CASSANDRA-19022:
--------------------------------------------
[~smiklosovic] would it be possible here to backport the direct memory fix to
5.0? Currently, 'nodetool gcstats' reports -1 for direct memory.
> 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: 1h
> 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: [email protected]
For additional commands, e-mail: [email protected]
