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

Brad Schoening updated CASSANDRA-18454:
---------------------------------------
    Change Category: Operability
         Complexity: Low Hanging Fruit
             Status: Open  (was: Triage Needed)

> Enhance nodetool gcstats 
> -------------------------
>
>                 Key: CASSANDRA-18454
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18454
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tool/nodetool
>            Reporter: Brad Schoening
>            Priority: Normal
>
> Nodetool gcstats provides only a brief one line output of historical GC 
> activity with Max, Total, Stdev, etc
> {noformat}
> % nodetool gcstats
>        Interval (ms) Max GC Elapsed (ms)Total GC Elapsed (ms)Stdev GC Elapsed 
> (ms)   GC Reclaimed (MB)         Collections      Direct Memory Bytes
>                11979                   0                   0                 
> NaN                   0                   0                       -1
> {noformat}
> Performance of garbage collection is such an key part of Cassandra 
> performance that it would be helpful to have more complete metrics with 
> *gcstats* here.  The MBean java.lang.GarbageCollector has recent statistic 
> which could be added in events/second for:
>  * GcThreadCount
>  * Duration
> The current size of eden / survivor / old space and humongous allocations 
> should be shown as well.
> The metrics show with jhsdb jmap would be very helpful as well, if they're 
> available.
> [https://docs.oracle.com/en/java/javase/11/troubleshoot/diagnostic-tools.html#GUID-A69901EC-F87D-4B63-A8B7-DE8684AD4FF9]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to