[GitHub] eagle pull request #933: EAGLE-1016: fix keyword "group" conflict in JDBC st...
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/933 --- 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-1016) Mysql table eagle_metric_eagle_metric_schema is having issue
[ https://issues.apache.org/jira/browse/EAGLE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016931#comment-16016931 ] ASF GitHub Bot commented on EAGLE-1016: --- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/933 > Mysql table eagle_metric_eagle_metric_schema is having issue > > > Key: EAGLE-1016 > URL: https://issues.apache.org/jira/browse/EAGLE-1016 > Project: Eagle > Issue Type: Bug >Reporter: vikash kumar >Assignee: Zhao, Qingwen > Attachments: Apache Eagle Error log.txt > > > Hi, > eagle_metric_eagle_metric_schema is having a column_name as "group" which is > a reserved keyword. I am getting an error as mysql syntax error near group > when i am trying to run the apache eagle application for > hadoop_metric_monitor. Initially i was getting error even in creating this > table with group keyword as column but i resolved it using group .Now it is > trying to write to some of the table which is having group as a cloumn_name. > That's why it is throwing error. Can somebody help me out. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #934: EAGLE-1022: Fix runtime exception when parsing spar...
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/934 --- 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-1024) Monitor jobs with high RPC throughput
[ https://issues.apache.org/jira/browse/EAGLE-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016919#comment-16016919 ] ASF GitHub Bot commented on EAGLE-1024: --- GitHub user qingwen220 opened a pull request: https://github.com/apache/eagle/pull/938 EAGLE-1024: Monitor jobs with high RPC throughput https://issues.apache.org/jira/browse/EAGLE-1024 * add job RPC data in MAP_REDUCE_JOB_STREAM * refactor org.apache.eagle.jpm.analyzer.publisher.EmailPublisher * support new config 'application.analyzerReport.alertLevel' to define alert level You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/eagle EAGLE-1024 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/938.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 #938 commit 5beddd6c55512570f20532f15d42d961b442cecf Author: Zhao, QingwenDate: 2017-05-18T15:02:57Z add JobRpcAnalysisEvaluator commit 9011e49fbd7d82b83e455dfdceebf1b4d1359eef Author: Zhao, Qingwen Date: 2017-05-19T05:29:20Z refactor EmailPublisher.java > Monitor jobs with high RPC throughput > -- > > Key: EAGLE-1024 > URL: https://issues.apache.org/jira/browse/EAGLE-1024 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > We've identified some jobs with high RPC throughput which causes the NN heavy > RPC overhead. These jobs has requested extremely large HDFS operations in a > very short window (2 mins). > So we tend to capture those jobs with: > a) the job has very large RPC throughput, using the job total HDFS ops/the > job duration, if the throughput is larger than 1000 > b) and if the HDFS ops per task is larger than 25 > Then send out the alert out. Later, we will notify the users to optimize > their jobs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #938: EAGLE-1024: Monitor jobs with high RPC throughput
GitHub user qingwen220 opened a pull request: https://github.com/apache/eagle/pull/938 EAGLE-1024: Monitor jobs with high RPC throughput https://issues.apache.org/jira/browse/EAGLE-1024 * add job RPC data in MAP_REDUCE_JOB_STREAM * refactor org.apache.eagle.jpm.analyzer.publisher.EmailPublisher * support new config 'application.analyzerReport.alertLevel' to define alert level You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/eagle EAGLE-1024 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/938.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 #938 commit 5beddd6c55512570f20532f15d42d961b442cecf Author: Zhao, QingwenDate: 2017-05-18T15:02:57Z add JobRpcAnalysisEvaluator commit 9011e49fbd7d82b83e455dfdceebf1b4d1359eef Author: Zhao, Qingwen Date: 2017-05-19T05:29:20Z refactor EmailPublisher.java --- 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] [Assigned] (EAGLE-1024) Monitor jobs with high RPC throughput
[ https://issues.apache.org/jira/browse/EAGLE-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen reassigned EAGLE-1024: Assignee: Zhao, Qingwen > Monitor jobs with high RPC throughput > -- > > Key: EAGLE-1024 > URL: https://issues.apache.org/jira/browse/EAGLE-1024 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > We've identified some jobs with high RPC throughput which causes the NN heavy > RPC overhead. These jobs has requested extremely large HDFS operations in a > very short window (2 mins). > So we tend to capture those jobs with: > a) the job has very large RPC throughput, using the job total HDFS ops/the > job duration, if the throughput is larger than 1000 > b) and if the HDFS ops per task is larger than 25 > Then send out the alert out. Later, we will notify the users to optimize > their jobs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (EAGLE-1027) Alert Eavluator : Siddhi SQL-‐Like Query should support Case-in-sensitivity
Aravind Gopal created EAGLE-1027: Summary: Alert Eavluator : Siddhi SQL-‐Like Query should support Case-in-sensitivity Key: EAGLE-1027 URL: https://issues.apache.org/jira/browse/EAGLE-1027 Project: Eagle Issue Type: Bug Components: Core::Alert Engine Affects Versions: v0.4.0 Reporter: Aravind Gopal Priority: Minor Hi Team, I am newbie to Eagle.. In my case im monitoring MY SQL Audit log, I defiened Upper case in Policy definition but my value is in lower case. So alert evaluator should evaluvates any upper or lower case. please look into it Thanks in advance... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #937: [MINOR] Sync 0.5 branch with master branch changes
Github user qingwen220 closed the pull request at: https://github.com/apache/eagle/pull/937 --- 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 #935: EAGLE-1023: Update jmx metric collector scripts
Github user qingwen220 commented on the issue: https://github.com/apache/eagle/pull/935 @jhsenjaliya updated. Thanks --- 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. ---