[
https://issues.apache.org/jira/browse/EAGLE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076635#comment-15076635
]
ASF GitHub Bot commented on EAGLE-97:
-------------------------------------
Github user yonzhang commented on the pull request:
https://github.com/apache/incubator-eagle/pull/50#issuecomment-168418035
can the data model for CMS GC events be also trimmed/modified for other GC
strategy for example g1?
> Enable GC Log monitoring for important service like hadoop namenode
> -------------------------------------------------------------------
>
> Key: EAGLE-97
> URL: https://issues.apache.org/jira/browse/EAGLE-97
> Project: Eagle
> Issue Type: New Feature
> Affects Versions: 0.3.0
> Reporter: Libin, Sun
> Assignee: Libin, Sun
>
> Garbage Collection Monitoring refers to the process of figuring out how JVM
> is running GC.
> When GC happened, JVM will stop the application from running to execute a GC,
> every thread except for the threads needed for the GC will stop their tasks.
> The interrupted tasks will resume only after the GC task has completed, the
> stop interval is known as "stop-the-world"
> For service like namenode, GC will affect the performance, especially full
> GC, we should avoid full GC and if full GC happened, we should detected it
> ASAP and sent out alert
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
