[jira] [Commented] (ACCUMULO-3770) Replace GarbageCollectionLogger with JVM provided GC stats

["Eric Newton (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ACCUMULO-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527154#comment-14527154 ] 

Eric Newton commented on ACCUMULO-3770:
---------------------------------------

Where do these reports go? Are they rolled-over like the regular logs?

The timeliness feature is nice, but that can be done in a separate SimpleTimer callback.

Knowing the status of GC in a long-running, time-sensitive server is very important. I would be hesitant to remove it.



> Replace GarbageCollectionLogger with JVM provided GC stats
> ----------------------------------------------------------
>
>                 Key: ACCUMULO-3770
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3770
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: tserver
>            Reporter: Josh Elser
>            Priority: Minor
>             Fix For: 1.8.0
>
>
> Hotspot provides some JVM opts that can be enabled which will print out status messages for garbage collection:
> {{-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -verbose:gc}}
> TabletServers have the {{GarbageCollectionLogger}} doing its own inspection of heap usage via {{Runtime}} and also tracking the real interval between calls to itself WRT the expected interval (to try to guess if there are issues getting resources to run code).
> As long as openjdk has support for the same options, I think removing the heap inspection would be good. Do we still want to preserve the "timeliness" check though? I'm not sure how valuable it is in real environments.
> Thoughts?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)