[
https://issues.apache.org/jira/browse/EAGLE-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879915#comment-15879915
]
ASF GitHub Bot commented on EAGLE-927:
--------------------------------------
GitHub user wujinhu reopened a pull request:
https://github.com/apache/eagle/pull/839
[EAGLE-927] support for hadoop jmx resource info
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wujinhu/eagle EAGLE-927
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/eagle/pull/839.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 #839
----
commit ddcd59616109caa7833af2d3e442cb9ad778ca28
Author: wujinhu <[email protected]>
Date: 2017-02-23T05:40:44Z
support for hadoop jmx resource info
----
> add jmx resource info to Hadoop JMX Monitor
> -------------------------------------------
>
> Key: EAGLE-927
> URL: https://issues.apache.org/jira/browse/EAGLE-927
> Project: Eagle
> Issue Type: Improvement
> Components: App::Hadoop JMX Monitor
> Affects Versions: v0.5.0
> Reporter: wujinhu
> Assignee: wujinhu
> Fix For: v0.5.0
>
>
> We need add an stream(HADOOP_JMX_RESOURCE_STREAM) to stand for jmx resource
> like corrupt files and live nodes and so on. For example, when we found
> missing block number via HADOOP_JMX_METRIC_STREAM by define a policy, we can
> find missing block id via HADOOP_JMX_RESOURCE_STREAM
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
