[
https://issues.apache.org/jira/browse/EAGLE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076487#comment-15076487
]
ASF GitHub Bot commented on EAGLE-97:
-------------------------------------
GitHub user sunlibin opened a pull request:
https://github.com/apache/incubator-eagle/pull/50
EAGLE-97 Enable GC Log monitoring
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sunlibin/incubator-eagle EAGLE-97
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/50.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #50
----
commit c1cae0c9119c743fb9b15e2c4c697fa4a3cecdf3
Author: sunlibin <[email protected]>
Date: 2016-01-01T15:34:10Z
EAGLE-97 Enable GC Log monitoring
----
> 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)
