[
https://issues.apache.org/jira/browse/EAGLE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076466#comment-15076466
]
Libin, Sun commented on EAGLE-97:
---------------------------------
>From above GC logs, we can generate gc puase time and heap usage metric
a) eagle.namenode.gc.pausetime
b) eagle.namenode.gc.memory.young.used
c) eagle.namenode.gc.memory.tenured.used
d) eagle.namenode.gc.memory.total.used
Also we can on board alert policies like following ones
{code:title=GC Pause Time Long alert}
from NNGCLogStream#window.externalTime(timestamp,10 min) select
sum(pausedGCTimeSec) as sumPausedSec having sumPausedSec >= 30 insert into
outputStream
{code}
{code:title=Full GC alert}
from NNGCLogStream[(permAreaGCed == true)] select * insert into outputStream;
{code}
> 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)
