[GitHub] eagle pull request #923: MINOR: rename 'HbaseServiceInstance' as 'HBaseServi...
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/923 --- 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-1012) Some language level problems
[ https://issues.apache.org/jira/browse/EAGLE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974168#comment-15974168 ] Benedict Jin commented on EAGLE-1012: - By the way, i am looking forward to the `Eagle` v0.5.0 :D > Some language level problems > > > Key: EAGLE-1012 > URL: https://issues.apache.org/jira/browse/EAGLE-1012 > Project: Eagle > Issue Type: Bug > Components: Project Infrastructure >Affects Versions: v0.4.0 > Environment: Linux 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 > EDT 2012 x86_64 x86_64 x86_64 GNU/Linux >Reporter: Benedict Jin > Labels: JDK > Fix For: v0.6.0 > > Attachments: Eagle Language Level Problems.txt > > Original Estimate: 168h > Remaining Estimate: 168h > > Some language level problems > * Spell > * Duplicated > * Lambda > * Collection > * String > * instanceof > * Complex Method > * Exception > Details see attachment files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-1012) Some language level problems
[ https://issues.apache.org/jira/browse/EAGLE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974164#comment-15974164 ] Benedict Jin commented on EAGLE-1012: - [~jhsenjaliya] Hi, Jayesh. Yep, i have installed `Eagle` v0.4.0 for monitoring `HDFS Audit` and `HBase Security`. Those imporvements about `Eagle` is based on newest master branch. As far as I know there is no any special tool for doing this. Maybe, some code quality CI tools could. And i think we should add a code quality tool into `Eagle` check-in system rather than just only `Jenkins`. Details about those problems will be recored in attachment files in succession. > Some language level problems > > > Key: EAGLE-1012 > URL: https://issues.apache.org/jira/browse/EAGLE-1012 > Project: Eagle > Issue Type: Bug > Components: Project Infrastructure >Affects Versions: v0.4.0 > Environment: Linux 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 > EDT 2012 x86_64 x86_64 x86_64 GNU/Linux >Reporter: Benedict Jin > Labels: JDK > Fix For: v0.6.0 > > Attachments: Eagle Language Level Problems.txt > > Original Estimate: 168h > Remaining Estimate: 168h > > Some language level problems > * Spell > * Duplicated > * Lambda > * Collection > * String > * instanceof > * Complex Method > * Exception > Details see attachment files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Issue Comment Deleted] (EAGLE-1012) Some language level problems
[ https://issues.apache.org/jira/browse/EAGLE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Jin updated EAGLE-1012: Comment: was deleted (was: [~jhsenjaliya] Hi, Jayesh. Yep, i have installed `Eagle` v0.4.0 for monitoring `HDFS Audit` and `HBase Security`. Those imporvements about `Eagle` is based on newest master branch. As far as I know there is no any special tool for doing this. Maybe, some code quality CI tools could. And i think we should add a code quality tool into `Eagle` check-in system rather than just only `Jenkins`. Details about those problems will be recored in attachment files in succession.) > Some language level problems > > > Key: EAGLE-1012 > URL: https://issues.apache.org/jira/browse/EAGLE-1012 > Project: Eagle > Issue Type: Bug > Components: Project Infrastructure >Affects Versions: v0.4.0 > Environment: Linux 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 > EDT 2012 x86_64 x86_64 x86_64 GNU/Linux >Reporter: Benedict Jin > Labels: JDK > Fix For: v0.6.0 > > Attachments: Eagle Language Level Problems.txt > > Original Estimate: 168h > Remaining Estimate: 168h > > Some language level problems > * Spell > * Duplicated > * Lambda > * Collection > * String > * instanceof > * Complex Method > * Exception > Details see attachment files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-1012) Some language level problems
[ https://issues.apache.org/jira/browse/EAGLE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974165#comment-15974165 ] Benedict Jin commented on EAGLE-1012: - Hi, [~jhsenjaliya]. Yep, i have installed `Eagle` v0.4.0 for monitoring `HDFS Audit` and `HBase Security`. Those imporvements about `Eagle` is based on newest master branch. As far as I know there is no any special tool for doing this. Maybe, some code quality CI tools could. And i think we should add a code quality tool into `Eagle` check-in system rather than just only `Jenkins`. Details about those problems will be recored in attachment files in succession. > Some language level problems > > > Key: EAGLE-1012 > URL: https://issues.apache.org/jira/browse/EAGLE-1012 > Project: Eagle > Issue Type: Bug > Components: Project Infrastructure >Affects Versions: v0.4.0 > Environment: Linux 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 > EDT 2012 x86_64 x86_64 x86_64 GNU/Linux >Reporter: Benedict Jin > Labels: JDK > Fix For: v0.6.0 > > Attachments: Eagle Language Level Problems.txt > > Original Estimate: 168h > Remaining Estimate: 168h > > Some language level problems > * Spell > * Duplicated > * Lambda > * Collection > * String > * instanceof > * Complex Method > * Exception > Details see attachment files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #923: MINOR: rename 'HbaseServiceInstance' as 'HBaseServi...
GitHub user qingwen220 opened a pull request: https://github.com/apache/eagle/pull/923 MINOR: rename 'HbaseServiceInstance' as 'HBaseServiceInstance' You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/eagle minor Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/923.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 #923 commit 20d7a1555f269c1e1728cd843e1369ae453deaa0 Author: Zhao, Qingwen Date: 2017-04-12T06:46:53Z refine app config commit 9a2871a7d2424e790a41833ad5b3eb541452b61c Author: Zhao, Qingwen Date: 2017-04-17T09:38:43Z Merge branch 'master' of https://github.com/qingwen220/incubator-eagle commit 7e1732e610e66f84199f15d2ae37bd7cb2d510dc Author: Zhao, Qingwen Date: 2017-04-18T08:55:16Z Merge branch 'master' of https://github.com/qingwen220/incubator-eagle commit 475f6be932b17278560b9a58599ea15e2e8c864e Author: Qingwen Zhao Date: 2017-04-19T06:05:03Z change 'HbaseServiceInstance' to 'HBaseServiceInstance' commit 2f83af03255c41f0d2de243d46b41ecd94bef920 Author: Qingwen Zhao Date: 2017-04-19T06:17:01Z update --- 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-446) convert eagle-hive app to use new app framework
[ https://issues.apache.org/jira/browse/EAGLE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiJun Tang resolved EAGLE-446. -- Resolution: Resolved > convert eagle-hive app to use new app framework > --- > > Key: EAGLE-446 > URL: https://issues.apache.org/jira/browse/EAGLE-446 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Edward Zhang >Assignee: Edward Zhang > Fix For: v0.5.0 > > > Existing eagle-hive application is a standalone storm application, we migrate > to manage using new application framework as part of whole eagle ecosystem. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-1012) Some language level problems
[ https://issues.apache.org/jira/browse/EAGLE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974138#comment-15974138 ] Jayesh commented on EAGLE-1012: --- are you on 0.4, any plan to move on to 0.5? or do this analysis for 0.5 as well ? btw, what is this tool ? do you have any detail report ? > Some language level problems > > > Key: EAGLE-1012 > URL: https://issues.apache.org/jira/browse/EAGLE-1012 > Project: Eagle > Issue Type: Bug > Components: Project Infrastructure >Affects Versions: v0.4.0 > Environment: Linux 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 > EDT 2012 x86_64 x86_64 x86_64 GNU/Linux >Reporter: Benedict Jin > Labels: JDK > Fix For: v0.6.0 > > Attachments: Eagle Language Level Problems.txt > > Original Estimate: 168h > Remaining Estimate: 168h > > Some language level problems > * Spell > * Duplicated > * Lambda > * Collection > * String > * instanceof > * Complex Method > * Exception > Details see attachment files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (EAGLE-928) Refine system metric schema design and fix system metric collector
[
https://issues.apache.org/jira/browse/EAGLE-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JiJun Tang resolved EAGLE-928.
--
Resolution: Resolved
> Refine system metric schema design and fix system metric collector
> --
>
> Key: EAGLE-928
> URL: https://issues.apache.org/jira/browse/EAGLE-928
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Refine system metric schema design and fix system metric collector
> h1. Principle
> Any metric (no mater sys metric) should at least have three fields: "metric",
> "group", "timestamp", "value",
> "group" is the metric category path separated with slash, for example "FIRST
> CATEGORY.SECOND CATEGORY", which will be commonly used for well organizing
> metric groups in customized metric dashboard.
> h1. Stream Name for System Metric
> {code}
>
> SYSTEM_METRIC_STREAM
> System Metrics Stream including CPU, Network, Disk,
> etc.
>
>
> host
> string
>
>
> timestamp
> long
>
>
> metric
> string
>
>
> group
> string
>
>
> site
> string
>
>
> device
> string
>
>
> value
> double
> 0.0
>
>
>
> {code}
> h1. Stream Schema for System metric
>
>* *metric*: [STRING] metric name string
>* *group*: [STRING] metric group/type
>* *timestamp*: [LONG] metric generation time
>* *site*: [STRING] siteId
>* *host*: [STRING] source host name
>* *device*: [STRING] device name, like cpu
> h1. Sample CPU Metric
> {code}
> {
> "timestamp": 1487918913569,
> "metric": "system.cpu.usage",
> "group": "system.cpu",
> "site": "sandbox",
> "value": 0.058,
> "host": "sandbox.hortonworks.com",
> "device": "cpu7"
> }
> {code}
> h1. Sample Network Metrics
> {code}
> {
> "timestamp": 1487918913569,
> "metric": "system.nic.transmitdrop",
> "group": "system.network",
> "site": "sandbox",
> "value": 7724.0,
> "host": "sandbox.hortonworks.com",
> "device": "eth0"
> }
> {code}
> h1. Sample Metric Schema
> {code}
> {
> "tags": {
> "site": "sandbox",
> "name": "system.memory.nfs_unstable.kb",
> "group": "system.memory"
> },
> "dimensionFields": [
> "host",
> "group",
> "site",
> "device"
> ],
> "metricFields": [
> "value"
> ],
> "granularity": "MINUTE",
> "modifiedTimestamp": 1488190388479
> }
> {code}
> h1. Stream Persist Topology
> {code}
> environment.newApp(config)
> .fromStream("HADOOP_JMX_METRIC_STREAM")
> .saveAsMetric(
> MetricDescriptor.metricGroupAs((MetricGroupSelector)
> event -> {
> if (event.containsKey("component")) {
> return String.format("hadoop.%s", ((String)
> event.get("component")).toLowerCase());
> } else {
> return "hadoop.metrics";
> }
> })
> .siteByField("site")
> .namedByField("metric")
> .eventTimeByField("timestamp")
> .dimensionFields("host", "component", "site")
> .granularity(Calendar.MINUTE)
> .valueField("value"))
> .fromStream("SYSTEM_METRIC_STREAM")
> .saveAsMetric(MetricDescriptor.metricGroupByField("group")
> .siteByField("site")
> .namedByField("metric")
> .eventTimeByField("timestamp")
> .dimensionFields("host", "group", "site", "device")
> .granularity(Calendar.MINUTE)
> .valueField("value")
> )
> .toTopology();
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (EAGLE-1012) Some language level problems
[ https://issues.apache.org/jira/browse/EAGLE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Jin updated EAGLE-1012: Attachment: Eagle Language Level Problems.txt > Some language level problems > > > Key: EAGLE-1012 > URL: https://issues.apache.org/jira/browse/EAGLE-1012 > Project: Eagle > Issue Type: Bug > Components: Project Infrastructure >Affects Versions: v0.4.0 > Environment: Linux 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 > EDT 2012 x86_64 x86_64 x86_64 GNU/Linux >Reporter: Benedict Jin > Labels: JDK > Fix For: v0.6.0 > > Attachments: Eagle Language Level Problems.txt > > Original Estimate: 168h > Remaining Estimate: 168h > > Some language level problems > * Spell > * Duplicated > * Lambda > * Collection > * String > * instanceof > * Complex Method > * Exception > Details see attachment files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (EAGLE-1012) Some language level problems
Benedict Jin created EAGLE-1012: --- Summary: Some language level problems Key: EAGLE-1012 URL: https://issues.apache.org/jira/browse/EAGLE-1012 Project: Eagle Issue Type: Bug Components: Project Infrastructure Affects Versions: v0.4.0 Environment: Linux 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux Reporter: Benedict Jin Fix For: v0.6.0 Some language level problems * Spell * Duplicated * Lambda * Collection * String * instanceof * Complex Method * Exception Details see attachment files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #922: [MINOR] Fix some project construction problems abou...
GitHub user asdf2014 opened a pull request: https://github.com/apache/eagle/pull/922 [MINOR] Fix some project construction problems about `test sources` Fix some project construction problems about `test sources` * "src/test/org.apache.eagle.xxx" -> "src/test/java/org.apache.eagle.xxx" Involved modules: * eagle-hbase-web * eagle-hdfs-web You can merge this pull request into a Git repository by running: $ git pull https://github.com/asdf2014/eagle project_infrastructure Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/922.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 #922 commit 2c2a7a31d885378975ad7e560f2d1759ad1b6c67 Author: asdf2014 <1571805...@qq.com> Date: 2017-04-19T04:02:22Z Fix some project construction problems about `test sources` --- 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-992) HBase Naming that unify `Hbase` and `HBase` into `HBase`
[ https://issues.apache.org/jira/browse/EAGLE-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Jin resolved EAGLE-992. Resolution: Fixed > HBase Naming that unify `Hbase` and `HBase` into `HBase` > > > Key: EAGLE-992 > URL: https://issues.apache.org/jira/browse/EAGLE-992 > Project: Eagle > Issue Type: Bug > Components: App::System Metric Monitor >Affects Versions: v0.4.0 >Reporter: Benedict Jin >Priority: Minor > Labels: patch > Fix For: v0.5.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > HBase Naming that unify `Hbase` and `HBase` into `HBase` -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (EAGLE-992) HBase Naming that unify `Hbase` and `HBase` into `HBase`
[ https://issues.apache.org/jira/browse/EAGLE-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Jin reopened EAGLE-992: > HBase Naming that unify `Hbase` and `HBase` into `HBase` > > > Key: EAGLE-992 > URL: https://issues.apache.org/jira/browse/EAGLE-992 > Project: Eagle > Issue Type: Bug > Components: App::System Metric Monitor >Affects Versions: v0.4.0 >Reporter: Benedict Jin >Priority: Minor > Labels: patch > Fix For: v0.5.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > HBase Naming that unify `Hbase` and `HBase` into `HBase` -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (EAGLE-982) The log length has exceeded the limit of 4 MB in Travis
[ https://issues.apache.org/jira/browse/EAGLE-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Jin resolved EAGLE-982. Resolution: Fixed > The log length has exceeded the limit of 4 MB in Travis > --- > > Key: EAGLE-982 > URL: https://issues.apache.org/jira/browse/EAGLE-982 > Project: Eagle > Issue Type: Bug > Components: Project Infrastructure >Affects Versions: v0.4.0 > Environment: Travis >Reporter: Benedict Jin > Labels: CI > Fix For: v0.4.1 > > Attachments: travis_log.txt > > Original Estimate: 168h > Remaining Estimate: 168h > > Maven throw too many warnings for checking `Code Style` in `Travis`. Should > we disable it for a while until we fix those `Code Style` issues? > ``` > The log length has exceeded the limit of 4 MB (this usually means that the > test suite is raising the same exception over and over). > The job has been terminated > ``` -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (EAGLE-981) GC overhead limit exceeded
[ https://issues.apache.org/jira/browse/EAGLE-981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Jin resolved EAGLE-981. Resolution: Fixed > GC overhead limit exceeded > -- > > Key: EAGLE-981 > URL: https://issues.apache.org/jira/browse/EAGLE-981 > Project: Eagle > Issue Type: Bug > Components: Project Infrastructure >Affects Versions: v0.4.0 > Environment: Travis >Reporter: Benedict Jin > Labels: CI > Fix For: v0.4.1 > > Attachments: gc_overhead.png > > Original Estimate: 24h > Remaining Estimate: 24h > > Travis throw `GC overhead limit exceeded` exception because the default `JVM` > option of maven limit the resource of Travis. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (EAGLE-992) HBase Naming that unify `Hbase` and `HBase` into `HBase`
[ https://issues.apache.org/jira/browse/EAGLE-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Jin closed EAGLE-992. -- Resolution: Fixed > HBase Naming that unify `Hbase` and `HBase` into `HBase` > > > Key: EAGLE-992 > URL: https://issues.apache.org/jira/browse/EAGLE-992 > Project: Eagle > Issue Type: Bug > Components: App::System Metric Monitor >Affects Versions: v0.4.0 >Reporter: Benedict Jin >Priority: Minor > Labels: patch > Fix For: v0.5.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > HBase Naming that unify `Hbase` and `HBase` into `HBase` -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (EAGLE-1011) Cannot read property '0' of undefined
[ https://issues.apache.org/jira/browse/EAGLE-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiJun Tang updated EAGLE-1011: -- Fix Version/s: (was: v0.5.0) > Cannot read property '0' of undefined > - > > Key: EAGLE-1011 > URL: https://issues.apache.org/jira/browse/EAGLE-1011 > Project: Eagle > Issue Type: Bug > Components: Core::Eagle Server >Affects Versions: v0.4.0 > Environment: Linux 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 > EDT 2012 x86_64 x86_64 x86_64 GNU/Linux >Reporter: Benedict Jin > Labels: serialization > Attachments: Apache Eagle Policy Detail Alert.png, Apache Eagle > Policy Detail Visualization.png > > Original Estimate: 168h > Remaining Estimate: 168h > > `Policy Detail - Visualization` > Those `Policy Eval Count` and `Alert Count` dashboards show `No Data > Available.` error messages, but I can be sure that "Eagle" has received some > alarm events. > It may due to the `TypeError` from `doc.js`. > ```js > TypeError: Cannot read property '0' of undefined > at doc.js:7626 > at doc.js:251 > at m.$eval (doc.js:266) > at m.$digest (doc.js:263) > at m.$apply (doc.js:266) > at g (doc.js:219) > at t (doc.js:223) > at XMLHttpRequest.u.onload (doc.js:224) > ``` -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (EAGLE-1011) Cannot read property '0' of undefined
[ https://issues.apache.org/jira/browse/EAGLE-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Jin updated EAGLE-1011: Attachment: Apache Eagle Policy Detail Alert.png > Cannot read property '0' of undefined > - > > Key: EAGLE-1011 > URL: https://issues.apache.org/jira/browse/EAGLE-1011 > Project: Eagle > Issue Type: Bug > Components: Core::Eagle Server >Affects Versions: v0.4.0 > Environment: Linux 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 > EDT 2012 x86_64 x86_64 x86_64 GNU/Linux >Reporter: Benedict Jin > Labels: serialization > Fix For: v0.5.0 > > Attachments: Apache Eagle Policy Detail Alert.png, Apache Eagle > Policy Detail Visualization.png > > Original Estimate: 168h > Remaining Estimate: 168h > > `Policy Detail - Visualization` > Those `Policy Eval Count` and `Alert Count` dashboards show `No Data > Available.` error messages, but I can be sure that "Eagle" has received some > alarm events. > It may due to the `TypeError` from `doc.js`. > ```js > TypeError: Cannot read property '0' of undefined > at doc.js:7626 > at doc.js:251 > at m.$eval (doc.js:266) > at m.$digest (doc.js:263) > at m.$apply (doc.js:266) > at g (doc.js:219) > at t (doc.js:223) > at XMLHttpRequest.u.onload (doc.js:224) > ``` -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (EAGLE-1011) Cannot read property '0' of undefined
[ https://issues.apache.org/jira/browse/EAGLE-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Jin updated EAGLE-1011: Attachment: (was: Apache Eagle Policy Detail Alert.png) > Cannot read property '0' of undefined > - > > Key: EAGLE-1011 > URL: https://issues.apache.org/jira/browse/EAGLE-1011 > Project: Eagle > Issue Type: Bug > Components: Core::Eagle Server >Affects Versions: v0.4.0 > Environment: Linux 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 > EDT 2012 x86_64 x86_64 x86_64 GNU/Linux >Reporter: Benedict Jin > Labels: serialization > Fix For: v0.5.0 > > Attachments: Apache Eagle Policy Detail Alert.png, Apache Eagle > Policy Detail Visualization.png > > Original Estimate: 168h > Remaining Estimate: 168h > > `Policy Detail - Visualization` > Those `Policy Eval Count` and `Alert Count` dashboards show `No Data > Available.` error messages, but I can be sure that "Eagle" has received some > alarm events. > It may due to the `TypeError` from `doc.js`. > ```js > TypeError: Cannot read property '0' of undefined > at doc.js:7626 > at doc.js:251 > at m.$eval (doc.js:266) > at m.$digest (doc.js:263) > at m.$apply (doc.js:266) > at g (doc.js:219) > at t (doc.js:223) > at XMLHttpRequest.u.onload (doc.js:224) > ``` -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (EAGLE-1011) Cannot read property '0' of undefined
[ https://issues.apache.org/jira/browse/EAGLE-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Jin updated EAGLE-1011: Description: `Policy Detail - Visualization` Those `Policy Eval Count` and `Alert Count` dashboards show `No Data Available.` error messages, but I can be sure that "Eagle" has received some alarm events. It may due to the `TypeError` from `doc.js`. ```js TypeError: Cannot read property '0' of undefined at doc.js:7626 at doc.js:251 at m.$eval (doc.js:266) at m.$digest (doc.js:263) at m.$apply (doc.js:266) at g (doc.js:219) at t (doc.js:223) at XMLHttpRequest.u.onload (doc.js:224) ``` was: `Policy Detail - Visualization` The `Policy Eval Count` and `Alert Count` dashboards show `No Data Available.` error messages, but I can be sure that "Eagle" has received some alarm events. It may due to the `TypeError` from `doc.js`. ```js TypeError: Cannot read property '0' of undefined at doc.js:7626 at doc.js:251 at m.$eval (doc.js:266) at m.$digest (doc.js:263) at m.$apply (doc.js:266) at g (doc.js:219) at t (doc.js:223) at XMLHttpRequest.u.onload (doc.js:224) ``` > Cannot read property '0' of undefined > - > > Key: EAGLE-1011 > URL: https://issues.apache.org/jira/browse/EAGLE-1011 > Project: Eagle > Issue Type: Bug > Components: Core::Eagle Server >Affects Versions: v0.4.0 > Environment: Linux 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 > EDT 2012 x86_64 x86_64 x86_64 GNU/Linux >Reporter: Benedict Jin > Labels: serialization > Fix For: v0.5.0 > > Attachments: Apache Eagle Policy Detail Alert.png, Apache Eagle > Policy Detail Visualization.png > > Original Estimate: 168h > Remaining Estimate: 168h > > `Policy Detail - Visualization` > Those `Policy Eval Count` and `Alert Count` dashboards show `No Data > Available.` error messages, but I can be sure that "Eagle" has received some > alarm events. > It may due to the `TypeError` from `doc.js`. > ```js > TypeError: Cannot read property '0' of undefined > at doc.js:7626 > at doc.js:251 > at m.$eval (doc.js:266) > at m.$digest (doc.js:263) > at m.$apply (doc.js:266) > at g (doc.js:219) > at t (doc.js:223) > at XMLHttpRequest.u.onload (doc.js:224) > ``` -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (EAGLE-1011) Cannot read property '0' of undefined
Benedict Jin created EAGLE-1011: --- Summary: Cannot read property '0' of undefined Key: EAGLE-1011 URL: https://issues.apache.org/jira/browse/EAGLE-1011 Project: Eagle Issue Type: Bug Components: Core::Eagle Server Affects Versions: v0.4.0 Environment: Linux 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux Reporter: Benedict Jin Fix For: v0.5.0 Attachments: Apache Eagle Policy Detail Alert.png, Apache Eagle Policy Detail Visualization.png `Policy Detail - Visualization` The `Policy Eval Count` and `Alert Count` dashboards show `No Data Available.` error messages, but I can be sure that "Eagle" has received some alarm events. It may due to the `TypeError` from `doc.js`. ```js TypeError: Cannot read property '0' of undefined at doc.js:7626 at doc.js:251 at m.$eval (doc.js:266) at m.$digest (doc.js:263) at m.$apply (doc.js:266) at g (doc.js:219) at t (doc.js:223) at XMLHttpRequest.u.onload (doc.js:224) ``` -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (EAGLE-1009) `return` inside `finally` block may result in losing exception
[ https://issues.apache.org/jira/browse/EAGLE-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict Jin updated EAGLE-1009: Summary: `return` inside `finally` block may result in losing exception (was: `return` inside `finally` block will result in losing exception) > `return` inside `finally` block may result in losing exception > -- > > Key: EAGLE-1009 > URL: https://issues.apache.org/jira/browse/EAGLE-1009 > Project: Eagle > Issue Type: Bug > Components: Project Infrastructure >Affects Versions: v0.4.0 >Reporter: Benedict Jin > Labels: JDK > Fix For: v0.5.0 > > Attachments: FinallyTest.java > > Original Estimate: 24h > Remaining Estimate: 24h > > `return` inside `finally` block will result in losing exception: > * If the finally block completes abruptly for reason S, then the try > statement completes abruptly for reason S (and the throw of value V is > discarded and forgotten). > * If the finally block completes abruptly for reason S, then the try > statement completes abruptly for reason S (and reason R is discarded). > reference: > http://docs.oracle.com/javase/specs/jls/se8/html/jls-14.html#jls-14.20.2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-1009) `return` inside `finally` block will result in losing exception
[ https://issues.apache.org/jira/browse/EAGLE-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972523#comment-15972523 ] ASF GitHub Bot commented on EAGLE-1009: --- Github user asdf2014 commented on the issue: https://github.com/apache/eagle/pull/920 @qingwen220 Hi, qingwen220. You are right. This situation will not lose any exception because all exception from `try` statement will be catched in `catch` block and it just print the exception message by `slf4j` in here. > `return` inside `finally` block will result in losing exception > --- > > Key: EAGLE-1009 > URL: https://issues.apache.org/jira/browse/EAGLE-1009 > Project: Eagle > Issue Type: Bug > Components: Project Infrastructure >Affects Versions: v0.4.0 >Reporter: Benedict Jin > Labels: JDK > Fix For: v0.5.0 > > Attachments: FinallyTest.java > > Original Estimate: 24h > Remaining Estimate: 24h > > `return` inside `finally` block will result in losing exception: > * If the finally block completes abruptly for reason S, then the try > statement completes abruptly for reason S (and the throw of value V is > discarded and forgotten). > * If the finally block completes abruptly for reason S, then the try > statement completes abruptly for reason S (and reason R is discarded). > reference: > http://docs.oracle.com/javase/specs/jls/se8/html/jls-14.html#jls-14.20.2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #920: [EAGLE-1009] Fix losing exception issues
Github user asdf2014 commented on the issue: https://github.com/apache/eagle/pull/920 @qingwen220 Hi, qingwen220. You are right. This situation will not lose any exception because all exception from `try` statement will be catched in `catch` block and it just print the exception message by `slf4j` in here. --- 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 pull request #921: [MINOR]Add license and exclude file end with sdl.
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/921 --- 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-1009) `return` inside `finally` block will result in losing exception
[ https://issues.apache.org/jira/browse/EAGLE-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972510#comment-15972510 ] ASF GitHub Bot commented on EAGLE-1009: --- Github user qingwen220 commented on the issue: https://github.com/apache/eagle/pull/920 I don't think there are exceptions lost in the code you modified. All these try statements are followed by catch statement which doesn't throw a new exception anymore. I agree with your idea that DON'T return in finally block > `return` inside `finally` block will result in losing exception > --- > > Key: EAGLE-1009 > URL: https://issues.apache.org/jira/browse/EAGLE-1009 > Project: Eagle > Issue Type: Bug > Components: Project Infrastructure >Affects Versions: v0.4.0 >Reporter: Benedict Jin > Labels: JDK > Fix For: v0.5.0 > > Attachments: FinallyTest.java > > Original Estimate: 24h > Remaining Estimate: 24h > > `return` inside `finally` block will result in losing exception: > * If the finally block completes abruptly for reason S, then the try > statement completes abruptly for reason S (and the throw of value V is > discarded and forgotten). > * If the finally block completes abruptly for reason S, then the try > statement completes abruptly for reason S (and reason R is discarded). > reference: > http://docs.oracle.com/javase/specs/jls/se8/html/jls-14.html#jls-14.20.2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #920: [EAGLE-1009] Fix losing exception issues
Github user qingwen220 commented on the issue: https://github.com/apache/eagle/pull/920 I don't think there are exceptions lost in the code you modified. All these try statements are followed by catch statement which doesn't throw a new exception anymore. I agree with your idea that DON'T return in finally block --- 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] [Deleted] (EAGLE-1010) Fix bugs introduced by EAGLE-992
[ https://issues.apache.org/jira/browse/EAGLE-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen deleted EAGLE-1010: - > Fix bugs introduced by EAGLE-992 > > > Key: EAGLE-1010 > URL: https://issues.apache.org/jira/browse/EAGLE-1010 > Project: Eagle > Issue Type: Sub-task >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > As the changes have not been tested thoroughly, some bugs have introduced. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (EAGLE-1010) Fix bugs introduced by EAGLE-992
Zhao, Qingwen created EAGLE-1010: Summary: Fix bugs introduced by EAGLE-992 Key: EAGLE-1010 URL: https://issues.apache.org/jira/browse/EAGLE-1010 Project: Eagle Issue Type: Sub-task Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen As the changes have not been tested thoroughly, some bugs have introduced. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #921: [MINOR]Add license and exclude file end with sdl.
GitHub user chitin opened a pull request: https://github.com/apache/eagle/pull/921 [MINOR]Add license and exclude file end with sdl. Add license and exclude file end with sdl. You can merge this pull request into a Git repository by running: $ git pull https://github.com/chitin/eagle fix998 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/921.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 #921 commit 5391c08078fc5c8b62b635d0739f1de7e2f12664 Author: chitin Date: 2017-04-18T09:22:26Z Add license and exclude file end with sdl. --- 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 pull request #920: [EAGLE-1009] Fix losing exception issues
GitHub user asdf2014 opened a pull request: https://github.com/apache/eagle/pull/920 [EAGLE-1009] Fix losing exception issues `return` inside `finally` block will result in losing exception: * If the finally block completes abruptly for reason S, then the try statement completes abruptly for reason S (and the throw of value V is discarded and forgotten). * If the finally block completes abruptly for reason S, then the try statement completes abruptly for reason S (and reason R is discarded). reference: http://docs.oracle.com/javase/specs/jls/se8/html/jls-14.html#jls-14.20.2 (https://issues.apache.org/jira/browse/EAGLE-1009) You can merge this pull request into a Git repository by running: $ git pull https://github.com/asdf2014/eagle return_inside_finally Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/920.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 #920 commit d7c2e08b0bac07e3da397fc7843e5bd49db5f896 Author: asdf2014 <1571805...@qq.com> Date: 2017-04-18T09:16:54Z Fix losing exception issues --- 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-1009) `return` inside `finally` block will result in losing exception
[ https://issues.apache.org/jira/browse/EAGLE-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972384#comment-15972384 ] ASF GitHub Bot commented on EAGLE-1009: --- GitHub user asdf2014 opened a pull request: https://github.com/apache/eagle/pull/920 [EAGLE-1009] Fix losing exception issues `return` inside `finally` block will result in losing exception: * If the finally block completes abruptly for reason S, then the try statement completes abruptly for reason S (and the throw of value V is discarded and forgotten). * If the finally block completes abruptly for reason S, then the try statement completes abruptly for reason S (and reason R is discarded). reference: http://docs.oracle.com/javase/specs/jls/se8/html/jls-14.html#jls-14.20.2 (https://issues.apache.org/jira/browse/EAGLE-1009) You can merge this pull request into a Git repository by running: $ git pull https://github.com/asdf2014/eagle return_inside_finally Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/920.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 #920 commit d7c2e08b0bac07e3da397fc7843e5bd49db5f896 Author: asdf2014 <1571805...@qq.com> Date: 2017-04-18T09:16:54Z Fix losing exception issues > `return` inside `finally` block will result in losing exception > --- > > Key: EAGLE-1009 > URL: https://issues.apache.org/jira/browse/EAGLE-1009 > Project: Eagle > Issue Type: Bug > Components: Project Infrastructure >Affects Versions: v0.4.0 >Reporter: Benedict Jin > Labels: JDK > Fix For: v0.5.0 > > Attachments: FinallyTest.java > > Original Estimate: 24h > Remaining Estimate: 24h > > `return` inside `finally` block will result in losing exception: > * If the finally block completes abruptly for reason S, then the try > statement completes abruptly for reason S (and the throw of value V is > discarded and forgotten). > * If the finally block completes abruptly for reason S, then the try > statement completes abruptly for reason S (and reason R is discarded). > reference: > http://docs.oracle.com/javase/specs/jls/se8/html/jls-14.html#jls-14.20.2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (EAGLE-1009) `return` inside `finally` block will result in losing exception
Benedict Jin created EAGLE-1009: --- Summary: `return` inside `finally` block will result in losing exception Key: EAGLE-1009 URL: https://issues.apache.org/jira/browse/EAGLE-1009 Project: Eagle Issue Type: Bug Components: Project Infrastructure Affects Versions: v0.4.0 Reporter: Benedict Jin Fix For: v0.5.0 Attachments: FinallyTest.java `return` inside `finally` block will result in losing exception: * If the finally block completes abruptly for reason S, then the try statement completes abruptly for reason S (and the throw of value V is discarded and forgotten). * If the finally block completes abruptly for reason S, then the try statement completes abruptly for reason S (and reason R is discarded). reference: http://docs.oracle.com/javase/specs/jls/se8/html/jls-14.html#jls-14.20.2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-1008) java.lang.NullPointerException in JHFEventReaderBase.close
[
https://issues.apache.org/jira/browse/EAGLE-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972340#comment-15972340
]
ASF GitHub Bot commented on EAGLE-1008:
---
Github user asfgit closed the pull request at:
https://github.com/apache/eagle/pull/919
> java.lang.NullPointerException in JHFEventReaderBase.close
> --
>
> Key: EAGLE-1008
> URL: https://issues.apache.org/jira/browse/EAGLE-1008
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> {code}
> 2017-04-17 19:53:31 Thread-8-mrHistoryJobSpout
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2Parser [ERROR] Caught
> exception parsing history file after 99 events
> java.io.IOException: java.lang.NullPointerException
> at
> org.apache.eagle.jpm.mr.history.parser.JHFEventReaderBase.close(JHFEventReaderBase.java:153)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2Parser.parse(JHFMRVer2Parser.java:65)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.crawler.DefaultJHFInputStreamCallback.onInputStream(DefaultJHFInputStreamCallback.java:60)
> [stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO.readFileContent(AbstractJobHistoryDAO.java:123)
> [stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.crawler.JHFCrawlerDriverImpl.crawl(JHFCrawlerDriverImpl.java:166)
> [stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.storm.JobHistorySpout.nextTuple(JobHistorySpout.java:166)
> [stormjar.jar:na]
> at
> backtype.storm.daemon.executor$fn__5629$fn__5644$fn__5673.invoke(executor.clj:585)
> [storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
> at backtype.storm.util$async_loop$fn__452.invoke(util.clj:465)
> [storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
> at clojure.lang.AFn.run(AFn.java:24) [clojure-1.5.1.jar:na]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
> Caused by: java.lang.NullPointerException: null
> at
> org.apache.eagle.jpm.util.jobcounter.JobCounters.getCounterValue(JobCounters.java:51)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.analyzer.mr.suggestion.MapReduceJobSuggestionContext.getMinimumIOSortMemory(MapReduceJobSuggestionContext.java:137)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.analyzer.mr.suggestion.MapReduceJobSuggestionContext.buildContext(MapReduceJobSuggestionContext.java:86)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.analyzer.mr.suggestion.MapReduceJobSuggestionContext.(MapReduceJobSuggestionContext.java:64)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.analyzer.mr.suggestion.JobSuggestionEvaluator.evaluate(JobSuggestionEvaluator.java:76)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.analyzer.mr.suggestion.JobSuggestionEvaluator.evaluate(JobSuggestionEvaluator.java:38)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.analyzer.mr.MRJobPerformanceAnalyzer.analyze(MRJobPerformanceAnalyzer.java:64)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.parser.JobSuggestionListener.flush(JobSuggestionListener.java:93)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.parser.JobEntityCreationPublisher.flush(JobEntityCreationPublisher.java:40)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.parser.JHFEventReaderBase.flush(JHFEventReaderBase.java:159)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.parser.JHFEventReaderBase.close(JHFEventReaderBase.java:150)
> ~[stormjar.jar:na]
> ... 9 common frames omitted
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] eagle pull request #919: EAGLE-1008: java.lang.NullPointerException in JHFEv...
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/919 --- 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-1008) java.lang.NullPointerException in JHFEventReaderBase.close
[
https://issues.apache.org/jira/browse/EAGLE-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972299#comment-15972299
]
ASF GitHub Bot commented on EAGLE-1008:
---
Github user jhsenjaliya commented on the issue:
https://github.com/apache/eagle/pull/919
@qingwen220, looks like this PR needs to be rebased ( since u created it
from ur other branch )
> java.lang.NullPointerException in JHFEventReaderBase.close
> --
>
> Key: EAGLE-1008
> URL: https://issues.apache.org/jira/browse/EAGLE-1008
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> {code}
> 2017-04-17 19:53:31 Thread-8-mrHistoryJobSpout
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2Parser [ERROR] Caught
> exception parsing history file after 99 events
> java.io.IOException: java.lang.NullPointerException
> at
> org.apache.eagle.jpm.mr.history.parser.JHFEventReaderBase.close(JHFEventReaderBase.java:153)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2Parser.parse(JHFMRVer2Parser.java:65)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.crawler.DefaultJHFInputStreamCallback.onInputStream(DefaultJHFInputStreamCallback.java:60)
> [stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO.readFileContent(AbstractJobHistoryDAO.java:123)
> [stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.crawler.JHFCrawlerDriverImpl.crawl(JHFCrawlerDriverImpl.java:166)
> [stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.storm.JobHistorySpout.nextTuple(JobHistorySpout.java:166)
> [stormjar.jar:na]
> at
> backtype.storm.daemon.executor$fn__5629$fn__5644$fn__5673.invoke(executor.clj:585)
> [storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
> at backtype.storm.util$async_loop$fn__452.invoke(util.clj:465)
> [storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
> at clojure.lang.AFn.run(AFn.java:24) [clojure-1.5.1.jar:na]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
> Caused by: java.lang.NullPointerException: null
> at
> org.apache.eagle.jpm.util.jobcounter.JobCounters.getCounterValue(JobCounters.java:51)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.analyzer.mr.suggestion.MapReduceJobSuggestionContext.getMinimumIOSortMemory(MapReduceJobSuggestionContext.java:137)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.analyzer.mr.suggestion.MapReduceJobSuggestionContext.buildContext(MapReduceJobSuggestionContext.java:86)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.analyzer.mr.suggestion.MapReduceJobSuggestionContext.(MapReduceJobSuggestionContext.java:64)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.analyzer.mr.suggestion.JobSuggestionEvaluator.evaluate(JobSuggestionEvaluator.java:76)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.analyzer.mr.suggestion.JobSuggestionEvaluator.evaluate(JobSuggestionEvaluator.java:38)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.analyzer.mr.MRJobPerformanceAnalyzer.analyze(MRJobPerformanceAnalyzer.java:64)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.parser.JobSuggestionListener.flush(JobSuggestionListener.java:93)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.parser.JobEntityCreationPublisher.flush(JobEntityCreationPublisher.java:40)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.parser.JHFEventReaderBase.flush(JHFEventReaderBase.java:159)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.parser.JHFEventReaderBase.close(JHFEventReaderBase.java:150)
> ~[stormjar.jar:na]
> ... 9 common frames omitted
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] eagle issue #905: HBase Naming that unify `Hbase` and `HBase` into `HBase`
Github user asdf2014 commented on the issue: https://github.com/apache/eagle/pull/905 @jhsenjaliya Okey, i got it. --- 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 #919: EAGLE-1008: java.lang.NullPointerException in JHFEventRead...
Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/919 @qingwen220, looks like this PR needs to be rebased ( since u created it from ur other branch ) --- 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-992) HBase Naming that unify `Hbase` and `HBase` into `HBase`
[ https://issues.apache.org/jira/browse/EAGLE-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972296#comment-15972296 ] ASF GitHub Bot commented on EAGLE-992: -- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/905 > HBase Naming that unify `Hbase` and `HBase` into `HBase` > > > Key: EAGLE-992 > URL: https://issues.apache.org/jira/browse/EAGLE-992 > Project: Eagle > Issue Type: Bug > Components: App::System Metric Monitor >Affects Versions: v0.4.0 >Reporter: Benedict Jin >Priority: Minor > Labels: patch > Fix For: v0.5.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > HBase Naming that unify `Hbase` and `HBase` into `HBase` -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #905: HBase Naming that unify `Hbase` and `HBase` into `H...
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/905 --- 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 #905: HBase Naming that unify `Hbase` and `HBase` into `HBase`
Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/905 @asdf2014 please add [MINOR] tag in pr title since there is not jira for this. --- 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-998) Add eagle csd
[ https://issues.apache.org/jira/browse/EAGLE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh resolved EAGLE-998. -- Resolution: Fixed we should add this in 0.5 release > Add eagle csd > - > > Key: EAGLE-998 > URL: https://issues.apache.org/jira/browse/EAGLE-998 > Project: Eagle > Issue Type: Improvement >Reporter: Lingang Deng >Assignee: Lingang Deng >Priority: Minor > Fix For: v0.5.0 > > > Add eagle-cdh in eagle-external, users who use cdh can integrate eagle to > cloudera manager. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (EAGLE-998) Add eagle csd
[ https://issues.apache.org/jira/browse/EAGLE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-998: - Fix Version/s: (was: v0.6.0) v0.5.0 > Add eagle csd > - > > Key: EAGLE-998 > URL: https://issues.apache.org/jira/browse/EAGLE-998 > Project: Eagle > Issue Type: Improvement >Reporter: Lingang Deng >Assignee: Lingang Deng >Priority: Minor > Fix For: v0.5.0 > > > Add eagle-cdh in eagle-external, users who use cdh can integrate eagle to > cloudera manager. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-998) Add eagle csd
[ https://issues.apache.org/jira/browse/EAGLE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972292#comment-15972292 ] ASF GitHub Bot commented on EAGLE-998: -- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/908 > Add eagle csd > - > > Key: EAGLE-998 > URL: https://issues.apache.org/jira/browse/EAGLE-998 > Project: Eagle > Issue Type: Improvement >Reporter: Lingang Deng >Assignee: Lingang Deng >Priority: Minor > Fix For: v0.6.0 > > > Add eagle-cdh in eagle-external, users who use cdh can integrate eagle to > cloudera manager. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #908: [EAGLE-998]Add eagle csd
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/908 --- 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. ---
