[jira] [Created] (EAGLE-949) JPM support job level suggestion
Jilin, Jiang created EAGLE-949: -- Summary: JPM support job level suggestion Key: EAGLE-949 URL: https://issues.apache.org/jira/browse/EAGLE-949 Project: Eagle Issue Type: Improvement Reporter: Jilin, Jiang Assignee: Jilin, Jiang -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (EAGLE-945) JPM support queue level overview
[ https://issues.apache.org/jira/browse/EAGLE-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on EAGLE-945 started by Jilin, Jiang. -- > JPM support queue level overview > > > Key: EAGLE-945 > URL: https://issues.apache.org/jira/browse/EAGLE-945 > Project: Eagle > Issue Type: Task >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > > JPM support queue level overview -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (EAGLE-945) JPM support queue level overview
[ https://issues.apache.org/jira/browse/EAGLE-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jilin, Jiang resolved EAGLE-945. Resolution: Fixed > JPM support queue level overview > > > Key: EAGLE-945 > URL: https://issues.apache.org/jira/browse/EAGLE-945 > Project: Eagle > Issue Type: Task >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > > JPM support queue level overview -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (EAGLE-948) can not package by maven
Han Hui Wen created EAGLE-948: -- Summary: can not package by maven Key: EAGLE-948 URL: https://issues.apache.org/jira/browse/EAGLE-948 Project: Eagle Issue Type: Bug Components: Core::Alert Engine Affects Versions: v0.5.0 Environment: JDK：jdk1.8.0_111 Maven ：apache-maven-3.3.9 OS:windows7 Reporter: Han Hui Wen Priority: Blocker Fix For: v0.5.0 When I package eagle ,find following error : [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile (default-compile) on project eagle-common: Compilation fai lure -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile (default-c ompile) on project eagle-common: Compilation failure at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: Compilation failure at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:976) at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) ... 20 more [ERROR] [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :eagle-common -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #864: [EAGLE-947] Publishers with same policy but different sche...
Github user RalphSu commented on the issue: https://github.com/apache/eagle/pull/864 @wujinhu @haoch Please help review this one. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] eagle issue #861: EAGLE-945 support queue in JPM overview
Github user qingwen220 commented on the issue: https://github.com/apache/eagle/pull/861 LGTM --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Resolved] (EAGLE-947) Publishers with same policy but different schema could produce duplicate alerts
[ https://issues.apache.org/jira/browse/EAGLE-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garrett Li resolved EAGLE-947. -- Resolution: Fixed fixed by PR - https://github.com/apache/eagle/pull/864 > Publishers with same policy but different schema could produce duplicate > alerts > --- > > Key: EAGLE-947 > URL: https://issues.apache.org/jira/browse/EAGLE-947 > Project: Eagle > Issue Type: Bug > Components: Core::Alert Engine >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > Assume that we have policy1 which have 2 kinds of output streams, one is > stream1 and another is stream2. If publisher1 is configured for policy1 and > stream1, and publisher2 is configured for policy1 and stream2, current code > will produce 2 alerts for either stream1 or stream2. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-947) Publishers with same policy but different schema could produce duplicate alerts
[ https://issues.apache.org/jira/browse/EAGLE-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904383#comment-15904383 ] ASF GitHub Bot commented on EAGLE-947: -- GitHub user garrettlish opened a pull request: https://github.com/apache/eagle/pull/864 [EAGLE-947] Publishers with same policy but different schema could produce duplicate alerts Assume that we have policy1 which have 2 kinds of output streams, one is stream1 and another is stream2. If publisher1 is configured for policy1 and stream1, and publisher2 is configured for policy1 and stream2, current code will produce 2 alerts for either stream1 or stream2. You can merge this pull request into a Git repository by running: $ git pull https://github.com/garrettlish/incubator-eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/864.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 #864 commit c51fa7c0b3bc8b82a8b1efb501bf97d7ea1d43fb Author: Xiancheng Li Date: 2017-03-10T03:49:16Z [EAGLE-947] Publishers with same policy but different schema could produce duplicate alerts Assume that we have policy1 which have 2 kinds of output streams, one is stream1 and another is stream2. If publisher1 is configured for policy1 and stream1, and publisher2 is configured for policy1 and stream2, current code will produce 2 alerts for either stream1 or stream2. > Publishers with same policy but different schema could produce duplicate > alerts > --- > > Key: EAGLE-947 > URL: https://issues.apache.org/jira/browse/EAGLE-947 > Project: Eagle > Issue Type: Bug > Components: Core::Alert Engine >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > Assume that we have policy1 which have 2 kinds of output streams, one is > stream1 and another is stream2. If publisher1 is configured for policy1 and > stream1, and publisher2 is configured for policy1 and stream2, current code > will produce 2 alerts for either stream1 or stream2. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #864: [EAGLE-947] Publishers with same policy but differe...
GitHub user garrettlish opened a pull request: https://github.com/apache/eagle/pull/864 [EAGLE-947] Publishers with same policy but different schema could produce duplicate alerts Assume that we have policy1 which have 2 kinds of output streams, one is stream1 and another is stream2. If publisher1 is configured for policy1 and stream1, and publisher2 is configured for policy1 and stream2, current code will produce 2 alerts for either stream1 or stream2. You can merge this pull request into a Git repository by running: $ git pull https://github.com/garrettlish/incubator-eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/864.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 #864 commit c51fa7c0b3bc8b82a8b1efb501bf97d7ea1d43fb Author: Xiancheng Li Date: 2017-03-10T03:49:16Z [EAGLE-947] Publishers with same policy but different schema could produce duplicate alerts Assume that we have policy1 which have 2 kinds of output streams, one is stream1 and another is stream2. If publisher1 is configured for policy1 and stream1, and publisher2 is configured for policy1 and stream2, current code will produce 2 alerts for either stream1 or stream2. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (EAGLE-947) Publishers with same policy but different schema could produce duplicate alerts
[ https://issues.apache.org/jira/browse/EAGLE-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garrett Li updated EAGLE-947: - Summary: Publishers with same policy but different schema could produce duplicate alerts (was: Publishers with different schema could produce duplicate alerts) > Publishers with same policy but different schema could produce duplicate > alerts > --- > > Key: EAGLE-947 > URL: https://issues.apache.org/jira/browse/EAGLE-947 > Project: Eagle > Issue Type: Bug > Components: Core::Alert Engine >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > Assume that we have policy1 which have 2 kinds of output streams, one is > stream1 and another is stream2. If publisher1 is configured for policy1 and > stream1, and publisher2 is configured for policy1 and stream2, current code > will produce 2 alerts for either stream1 or stream2. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (EAGLE-947) Publishers with different schema could produce duplicate alerts
[ https://issues.apache.org/jira/browse/EAGLE-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garrett Li updated EAGLE-947: - Description: Assume that we have policy1 which have 2 kinds of output streams, one is stream1 and another is stream2. If publisher1 is configured for policy1 and stream1, and publisher2 is configured for policy1 and stream2, current code will produce 2 alerts for either stream1 or stream2. > Publishers with different schema could produce duplicate alerts > --- > > Key: EAGLE-947 > URL: https://issues.apache.org/jira/browse/EAGLE-947 > Project: Eagle > Issue Type: Bug > Components: Core::Alert Engine >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > Assume that we have policy1 which have 2 kinds of output streams, one is > stream1 and another is stream2. If publisher1 is configured for policy1 and > stream1, and publisher2 is configured for policy1 and stream2, current code > will produce 2 alerts for either stream1 or stream2. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (EAGLE-947) Publishers with different schema could produce duplicate alerts
Garrett Li created EAGLE-947: Summary: Publishers with different schema could produce duplicate alerts Key: EAGLE-947 URL: https://issues.apache.org/jira/browse/EAGLE-947 Project: Eagle Issue Type: Bug Components: Core::Alert Engine Affects Versions: v0.5.0 Reporter: Garrett Li Assignee: Garrett Li Fix For: v0.5.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #863: [MINOR] fix sla job timezone issue
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/863 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (EAGLE-946) Refactor MRRunningJobApp & HadoopQueueApp
Zhao, Qingwen created EAGLE-946: --- Summary: Refactor MRRunningJobApp & HadoopQueueApp Key: EAGLE-946 URL: https://issues.apache.org/jira/browse/EAGLE-946 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Requirements 1. REST apis to the remote cluster should be called only once. 2. For each request, the fetch running apps should be limits -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (EAGLE-940) Hdfs RPC monitoring for per cluster/user
[
https://issues.apache.org/jira/browse/EAGLE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-940:
Description:
Monitor HDFS RPC requests at a cluster/user level. This feature leverage the
available data from the Kafka topic produced by the jmx metric collector
scripted.
Sample queries are listed, and the values are updated every minute
* the last minute statistics
http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.1m.count&pageSize=1000
* the last 5 minutes statistics
http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.5m.count&pageSize=1000
* the last 25 minutes statistics
http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.25m.count&pageSize=1000
was:
Monitor HDFS RPC requests at a cluster/user level. This feature leverage the
available data from the Kafka topic produced by the jmx metric collector
scripted.
Sample queries are listed
* the last minute statistics
http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.1m.count&pageSize=1000
* the last 5 minutes statistics
http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.5m.count&pageSize=1000
* the last 25 minutes statistics
http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.25m.count&pageSize=1000
> Hdfs RPC monitoring for per cluster/user
> -
>
> Key: EAGLE-940
> URL: https://issues.apache.org/jira/browse/EAGLE-940
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> Monitor HDFS RPC requests at a cluster/user level. This feature leverage the
> available data from the Kafka topic produced by the jmx metric collector
> scripted.
> Sample queries are listed, and the values are updated every minute
> * the last minute statistics
> http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.1m.count&pageSize=1000
> * the last 5 minutes statistics
> http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.5m.count&pageSize=1000
> * the last 25 minutes statistics
> http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.25m.count&pageSize=1000
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (EAGLE-940) Hdfs RPC monitoring for per cluster/user
[
https://issues.apache.org/jira/browse/EAGLE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-940:
Description:
Monitor HDFS RPC requests at a cluster/user level. This feature leverage the
available data from the Kafka topic produced by the jmx metric collector
scripted.
Sample queries are listed
* the last minute statistics
http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.1m.count&pageSize=1000
* the last 5 minutes statistics
http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.5m.count&pageSize=1000
* the last 25 minutes statistics
http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.25m.count&pageSize=1000
was:
* monitor HDFS RPC requests at a cluster/user level
* refactor all apps which consume namenode jmx
Up to now, the last minute statistics
http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.1m.count&pageSize=1000
Up to now, the last 5 minutes statistics
http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.5m.count&pageSize=1000
Up to now, the last 25 minutes statistics
http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.25m.count&pageSize=1000
> Hdfs RPC monitoring for per cluster/user
> -
>
> Key: EAGLE-940
> URL: https://issues.apache.org/jira/browse/EAGLE-940
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> Monitor HDFS RPC requests at a cluster/user level. This feature leverage the
> available data from the Kafka topic produced by the jmx metric collector
> scripted.
> Sample queries are listed
> * the last minute statistics
> http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.1m.count&pageSize=1000
> * the last 5 minutes statistics
> http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.5m.count&pageSize=1000
> * the last 25 minutes statistics
> http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.25m.count&pageSize=1000
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (EAGLE-940) Hdfs RPC monitoring for per cluster/user
[
https://issues.apache.org/jira/browse/EAGLE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-940:
Description:
* monitor HDFS RPC requests at a cluster/user level
* refactor all apps which consume namenode jmx
Up to now, the last minute statistics
http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.1m.count&pageSize=1000
Up to now, the last 5 minutes statistics
http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.5m.count&pageSize=1000
Up to now, the last 25 minutes statistics
http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.25m.count&pageSize=1000
was:
* monitor HDFS RPC requests at a cluster/user level
* refactor all apps which consume namenode jmx
> Hdfs RPC monitoring for per cluster/user
> -
>
> Key: EAGLE-940
> URL: https://issues.apache.org/jira/browse/EAGLE-940
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> * monitor HDFS RPC requests at a cluster/user level
> * refactor all apps which consume namenode jmx
> Up to now, the last minute statistics
> http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.1m.count&pageSize=1000
> Up to now, the last 5 minutes statistics
> http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.5m.count&pageSize=1000
> Up to now, the last 25 minutes statistics
> http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}&metricName=hadoop.hdfs.auditlog.25m.count&pageSize=1000
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] eagle pull request #863: [MINOR] fix sla job timezone issue
GitHub user wujinhu opened a pull request: https://github.com/apache/eagle/pull/863 [MINOR] fix sla job timezone issue You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/eagle EAGLE-851 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/863.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 #863 commit 6d3d47e52a8baf7208c3c7fff69eb36e95d1a3a0 Author: wujinhu Date: 2017-03-09T08:47:40Z fix sla job timezone issue --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (EAGLE-940) Hdfs RPC monitoring for per cluster/user
[ https://issues.apache.org/jira/browse/EAGLE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902686#comment-15902686 ] ASF GitHub Bot commented on EAGLE-940: -- GitHub user qingwen220 opened a pull request: https://github.com/apache/eagle/pull/862 EAGLE-940: HDFS traffic monitor by the namenode jmx data https://issues.apache.org/jira/browse/EAGLE-940 You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/incubator-eagle EAGLE-940 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/862.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 #862 > Hdfs RPC monitoring for per cluster/user > - > > Key: EAGLE-940 > URL: https://issues.apache.org/jira/browse/EAGLE-940 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > * monitor HDFS RPC requests at a cluster/user level > * refactor all apps which consume namenode jmx -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #862: EAGLE-940: HDFS traffic monitor by the namenode jmx...
GitHub user qingwen220 opened a pull request: https://github.com/apache/eagle/pull/862 EAGLE-940: HDFS traffic monitor by the namenode jmx data https://issues.apache.org/jira/browse/EAGLE-940 You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/incubator-eagle EAGLE-940 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/862.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 #862 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
