You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2010/10/15 18:12:33 UTC

[jira] Created: (CASSANDRA-1621) Show recent and total GC times in GCInspector

Show recent and total GC times in GCInspector
---------------------------------------------

                 Key: CASSANDRA-1621
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1621
             Project: Cassandra
          Issue Type: Improvement
          Components: Tools
            Reporter: Jonathan Ellis
            Assignee: Jonathan Ellis
            Priority: Minor
             Fix For: 0.6.7, 0.7.0


Showing GC times as something jconsole et al can graph can make correlating it with other system activity much easier than having it in either the jvm's log or log4j's.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (CASSANDRA-1621) Show recent and total GC times in GCInspector

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-1621.
---------------------------------------

    Resolution: Not A Problem
      Assignee:     (was: Jonathan Ellis)

This is already exposed by java.lang.GarbageCollector.*.CollectionTime attributes.

> Show recent and total GC times in GCInspector
> ---------------------------------------------
>
>                 Key: CASSANDRA-1621
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1621
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.6.7, 0.7.0
>
>
> Showing GC times as something jconsole et al can graph can make correlating it with other system activity much easier than having it in either the jvm's log or log4j's.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.