[
https://issues.apache.org/jira/browse/CASSANDRA-18454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868444#comment-17868444
]
Dhanush Ananthkar commented on CASSANDRA-18454:
-----------------------------------------------
{quote}GC Threads: 1
Duration: 15 ms
MemLock: false
G1HeapRegionSize: 16.000 MiB
OS Free Memory Bytes: 24.895 MiB
OS In Use: 15.976 GiB / 16.000 GiB (99.8%)
OS Swap In Use: 10.460 GiB / 11.000 GiB (95.1%)
Interval (ms) Max GC Elapsed (ms)Total GC Elapsed (ms)Stdev GC Elapsed
(ms) GC Reclaimed (MB) Collections Direct Memory Bytes
16129 13 13
0 380772632 1 -1
Heap memory used: 165.421 MiB (4.0%)
G1 Eden Space memory used: 96.000 MiB (20.7%)
G1 Old Gen memory used: 31.592 MiB (0.9%)
G1 Survivor Space memory used: 37.829 MiB (78.8%)
{quote}
> 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
> Assignee: Dhanush Ananthkar
> 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}
> 1. 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]
> 2. Since physical memory is also a critical part of GC performance, it would
> be useful to report the following MBeans
> |[cassandra_os_free_memory_bytes|https://github.com/instaclustr/cassandra-exporter/wiki/Exported-Metrics#_cassandra_os_free_memory_bytes]|Amount
> of free physical memory available (as seen by the Cassandra JVM process).|
> |[cassandra_os_free_swap_bytes|https://github.com/instaclustr/cassandra-exporter/wiki/Exported-Metrics#_cassandra_os_free_swap_bytes]|Amount
> of free swap space available (as seen by the Cassandra JVM process).|
> |[cassandra_os_memory_bytes_total|https://github.com/instaclustr/cassandra-exporter/wiki/Exported-Metrics#_cassandra_os_memory_bytes_total]|Total
> physical memory available (as seen by the Cassandra JVM process).|
> |[cassandra_os_swap_bytes_total|https://github.com/instaclustr/cassandra-exporter/wiki/Exported-Metrics#_cassandra_os_swap_bytes_total]|Total
> swap space available (as seen by the Cassandra JVM process).|
> or use
> [/proc/meminfo|https://stackoverflow.com/questions/59581597/get-available-ram-in-java]
> SystemInfo.java already reads /proc/<pid>/limits on Linux systems.
> 3. Status of memlock
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
