[jira] [Updated] (EAGLE-134) publish javadoc of eagle

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-134:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> publish javadoc of eagle
> 
>
> Key: EAGLE-134
> URL: https://issues.apache.org/jira/browse/EAGLE-134
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Michael Wu
>Assignee: Michael Wu
>Priority: Minor
> Fix For: v0.5.1
>
>
> try to find a way to publish javadoc



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-470) data enrichment refactor in eagle security monitoring

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-470:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> data enrichment refactor in eagle security monitoring
> -
>
> Key: EAGLE-470
> URL: https://issues.apache.org/jira/browse/EAGLE-470
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
> Fix For: v0.5.1
>
>
> Data enrichment happens in eagle security monitoring by retrieving 
> sensitivity data from eagle service and then join in real time.
> A lot of code is duplicated in current data enrich, this jira ticket is for 
> simplifying data enrichment.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-373) Move Eagle document to Eagle source code control

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-373:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> Move Eagle document to Eagle source code control
> 
>
> Key: EAGLE-373
> URL: https://issues.apache.org/jira/browse/EAGLE-373
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
> Fix For: v0.5.1
>
>
> Today Eagle's document is maintained in 
> https://github.com/eaglemonitoring/eaglemonitoring.github.io, it does not 
> conform to Apache policy. We should move this into Apache git source control. 
> The approach is to create a branch called document in 
> https://github.com/apache/incubator-eagle/tree/document and put document into 
> it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-973) update site document content

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-973:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> update site document content
> 
>
> Key: EAGLE-973
> URL: https://issues.apache.org/jira/browse/EAGLE-973
> Project: Eagle
>  Issue Type: Sub-task
>Reporter: Jayesh
>Assignee: Hao Chen
> Fix For: v0.5.1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-568) Set max retry times for HDFS problems, otherwise skip instead of blocking whole topology

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-568:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> Set max retry times for HDFS problems, otherwise skip instead of blocking 
> whole topology
> 
>
> Key: EAGLE-568
> URL: https://issues.apache.org/jira/browse/EAGLE-568
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: wujinhu
>  Labels: eagle-jpm, eagle-jpm-mr-history
> Fix For: v0.5.1
>
>
> h1. Problem and Exception
> {code}
> 2016-09-23 16:20:03 Thread-2-mrHistoryJobExecutor 
> org.apache.eagle.jpm.mr.history.storm.JobHistorySpout [ERROR] fail crawling 
> job history file and continue ...
> java.lang.RuntimeException: org.apache.hadoop.hdfs.BlockMissingException: 
> Could not obtain block: 
> BP-1687617170-10.8.211.11-1404135347814:blk_6965456919_1107923643088 
> file=/mapred/history/done/2016/09/23/000716/job_1470077190071_716284_conf.xml
> at 
> org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2398) 
> ~[stormjar.jar:na]
> at 
> org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2261) 
> ~[stormjar.jar:na]
> at 
> org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2168) 
> ~[stormjar.jar:na]
> at 
> org.apache.hadoop.conf.Configuration.iterator(Configuration.java:2210) 
> ~[stormjar.jar:na]
> at java.lang.Iterable.forEach(Iterable.java:74) ~[na:1.8.0_91]
> at org.apache.eagle.jpm.util.Utils.fetchJobType(Utils.java:112) 
> ~[stormjar.jar:na]
> at 
> org.apache.eagle.jpm.mr.history.parser.JHFEventReaderBase.(JHFEventReaderBase.java:121)
>  ~[stormjar.jar:na]
> at 
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2EventReader.(JHFMRVer2EventReader.java:47)
>  ~[stormjar.jar:na]
> at 
> org.apache.eagle.jpm.mr.history.parser.JHFParserFactory.getParser(JHFParserFactory.java:49)
>  ~[stormjar.jar:na]
> at 
> org.apache.eagle.jpm.mr.history.crawler.DefaultJHFInputStreamCallback.onInputStream(DefaultJHFInputStreamCallback.java:55)
>  ~[stormjar.jar:na]
> at 
> org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO.readFileContent(AbstractJobHistoryDAO.java:163)
>  ~[stormjar.jar:na]
> at 
> org.apache.eagle.jpm.mr.history.crawler.JHFCrawlerDriverImpl.crawl(JHFCrawlerDriverImpl.java:173)
>  ~[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: org.apache.hadoop.hdfs.BlockMissingException: Could not obtain 
> block: BP-1687617170-10.8.211.11-1404135347814:blk_6965456919_1107923643088 
> file=/mapred/history/done/2016/09/23/000716/job_1470077190071_716284_conf.xml
> at 
> org.apache.hadoop.hdfs.DFSInputStream.chooseDataNode(DFSInputStream.java:880) 
> ~[stormjar.jar:na]
> at 
> org.apache.hadoop.hdfs.DFSInputStream.blockSeekTo(DFSInputStream.java:560) 
> ~[stormjar.jar:na]
> at 
> org.apache.hadoop.hdfs.DFSInputStream.readWithStrategy(DFSInputStream.java:790)
>  ~[stormjar.jar:na]
> at 
> org.apache.hadoop.hdfs.DFSInputStream.read(DFSInputStream.java:837) 
> ~[stormjar.jar:na]
> at 
> org.apache.hadoop.hdfs.DFSInputStream.read(DFSInputStream.java:645) 
> ~[stormjar.jar:na]
> at java.io.FilterInputStream.read(FilterInputStream.java:83) 
> ~[na:1.8.0_91]
> at 
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager$RewindableInputStream.read(XMLEntityManager.java:2899)
>  ~[na:1.8.0_91]
> at 
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:674)
>  ~[na:1.8.0_91]
> at 
> com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:189)
>  ~[na:1.8.0_91]
> at 
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:812)
>  ~[na:1.8.0_91]
> at 
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
>  ~[na:1.8.0_91]
> at 
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
>  ~[na:1.8.0_91]
> at 
> 

[jira] [Updated] (EAGLE-850) fetch node usage from name node/resource manager jmx

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-850:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> fetch node usage from name node/resource manager jmx
> 
>
> Key: EAGLE-850
> URL: https://issues.apache.org/jira/browse/EAGLE-850
> Project: Eagle
>  Issue Type: Improvement
>  Components: App::Hadoop JMX Monitor
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: Michael Wu
> Fix For: v0.5.1
>
>
> fetch NodeUsage from jmx. The data in jmx looks like 
> NodeUsage: 
> "{"nodeUsage":{"min":"0.30%","median":"87.04%","max":"98.92%","stdDev":"31.67%"}}"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-666) Define fast compact data structure for kafka between application and alert engine

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-666:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> Define fast compact data structure for kafka between application and alert 
> engine
> -
>
> Key: EAGLE-666
> URL: https://issues.apache.org/jira/browse/EAGLE-666
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.1
>
>
> Define fast compact data structure for kafka between application and alert 
> engine



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-965) Eagle JPM Yarn Overview Chart Improvement

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-965:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> Eagle JPM Yarn Overview Chart Improvement
> -
>
> Key: EAGLE-965
> URL: https://issues.apache.org/jira/browse/EAGLE-965
> Project: Eagle
>  Issue Type: Bug
>  Components: App::Job Performance Monitor
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Jilin, Jiang
> Fix For: v0.5.1
>
>
> 1. Fix CPU Usage Unit/IO OPS on "Yarn Jobs/Overview" page, currently use 
> storage unit
> 2. Add chart legend and description under the chart about:
> 1) How Top-N is calculated and sorted?
> 2) Explain data point's value is 0?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-874) Improve hadoop jmx collector scripts

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-874:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> Improve hadoop jmx collector scripts
> 
>
> Key: EAGLE-874
> URL: https://issues.apache.org/jira/browse/EAGLE-874
> Project: Eagle
>  Issue Type: Improvement
>  Components: App::Hadoop JMX Monitor
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.1
>
>
> * Handle IPC metrics name for different version
> * Add JMX API query filter to reduce throughput from monitored service.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-509) make streaming application's sink type to be java bean

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-509:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> make streaming application's sink type to be java bean
> --
>
> Key: EAGLE-509
> URL: https://issues.apache.org/jira/browse/EAGLE-509
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.1
>
>
> Application's sink is used by alert engine, i.e. alert engine needs know each 
> field type for one sink.
> Sink type now is a Map type, which means developer has to configure each 
> field type in application descriptor file, that is boring and error-prone. If 
> we make sink type to be a java bean, then framework can automatically 
> generate field type to be used for defining alert metadata.
> Also with java bean, we can use annotation to customize more metadata, for 
> example use annotation to specify which field is timestamp column



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-1033) Help button not usable in web UI

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-1033:
--
Fix Version/s: (was: v0.5.0)
   v0.5.1

> Help button not usable in web UI
> 
>
> Key: EAGLE-1033
> URL: https://issues.apache.org/jira/browse/EAGLE-1033
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
> Environment: Cent 0S 6.8
> MySQL Community Server (GPL) 5.7.18
> x86_64 for linux
> eagle 0.5
> hadoop 2.6.4 
>Reporter: Alexandre
> Fix For: v0.5.1
>
>
> Hello,
> in the web UI of eagle when i click on the help button (in the top right 
> corner), the help menu is displayed ("How to start using eagle", "How to 
> register new site", "How to install application", "How to manage 
> application", "how to develop application", "Preview eagle metric"). But 
> nothing happen when i click on one of them.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-377) tomcat jar dependencies need to be cleaned up

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-377:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> tomcat jar dependencies need to be cleaned up
> -
>
> Key: EAGLE-377
> URL: https://issues.apache.org/jira/browse/EAGLE-377
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
> Fix For: v0.5.1
>
>
> There are 3 jars needing to be cleaned up in directory 
> eagle-assembly/src/main/lib/tomcat/bin, they are:
>  - bootstrap.jar
>  - commons-daemon.jar
>  - tomcat-juli.jar
> Currently, we use an approach to remove it before packaging a source code 
> tar-ball, and give customers a patch url to apply them back before building 
> from source. We'd better clean it up and form a smoother way in version 
> 0.5.0-incubating.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-260) Support to fetch audit log from http://localhost:50070/logs/hdfs-audit.log for quick preview

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-260:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> Support to fetch audit log from http://localhost:50070/logs/hdfs-audit.log 
> for quick preview
> 
>
> Key: EAGLE-260
> URL: https://issues.apache.org/jira/browse/EAGLE-260
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.1
>
>
> Support to fetch audit log from http://localhost:50070/logs/hdfs-audit.log 
> for quick preview



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-958) ElasticSearch Alert Publisher

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-958:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> ElasticSearch Alert Publisher
> -
>
> Key: EAGLE-958
> URL: https://issues.apache.org/jira/browse/EAGLE-958
> Project: Eagle
>  Issue Type: New Feature
>  Components: Core::Alert Engine
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.1
>
>
> ElasticSearch Alert Publisher



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-252) Remove dependency of AlertExecutorId in metadata while partitioning policy

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-252:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> Remove dependency of AlertExecutorId in metadata while partitioning policy
> --
>
> Key: EAGLE-252
> URL: https://issues.apache.org/jira/browse/EAGLE-252
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.1
>
>
> Remove dependency of AlertExecutorId in metadata while partitioning policy



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-481) Make alert engine topology to be one application so to be managed by Eagle API

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-481:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> Make alert engine topology to be one application so to be managed by Eagle API
> --
>
> Key: EAGLE-481
> URL: https://issues.apache.org/jira/browse/EAGLE-481
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.1
>
>
> Eagle alert engine as of 0.5 is multiple separate storm topologies. Instead 
> of running alert engine manually, we can leverage Eagle 0.5 application API 
> to manage alert engine. 
> Options:
> 1. Wrapper alert engine topology to be one Eagle application
> 2. Define a new service API to directly start/stop alert engine



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-611) Add User-Oriented Policy API

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-611:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> Add User-Oriented Policy API
> 
>
> Key: EAGLE-611
> URL: https://issues.apache.org/jira/browse/EAGLE-611
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.1
>
>
> Existing /metadata/policies API are internal-oriented instead of 
> user-oriented. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-256) Replace HDP version based hadoop dependencies with community version instead.

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-256:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> Replace HDP version based hadoop dependencies with community version instead.
> -
>
> Key: EAGLE-256
> URL: https://issues.apache.org/jira/browse/EAGLE-256
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
> Fix For: v0.5.1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-474) some improvements of app framework: appId naming, jarFile field, InstallOperation etc.

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-474:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> some improvements of app framework: appId naming, jarFile field, 
> InstallOperation etc.
> --
>
> Key: EAGLE-474
> URL: https://issues.apache.org/jira/browse/EAGLE-474
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
> Fix For: v0.5.1
>
>
> App framework has some bugs and also needs some improvement
> 1. appId in ApplicationEntity should not contain "[,]" chars, which will make 
> storm UI not show the topology details
> 2. jarPath is not necessary to be part of ApplicationDesc or metadata xml file
> 3. InstallOperation should contain jarPath which should be in the same level 
> of appType etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-768) AlertEngine: Policy Validation API doesn't evaluate the data source missing

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-768:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> AlertEngine: Policy Validation API doesn't evaluate the data source missing
> ---
>
> Key: EAGLE-768
> URL: https://issues.apache.org/jira/browse/EAGLE-768
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Garrett Li
> Fix For: v0.5.1
>
>
> Below scenario escape the policy validation,
> Policy Input Stream refers an invalid datasource.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-249) Support Postgres as hive metadata

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-249:
-
Fix Version/s: (was: v0.5.0)
   v0.5.1

> Support Postgres as hive metadata
> -
>
> Key: EAGLE-249
> URL: https://issues.apache.org/jira/browse/EAGLE-249
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Su Ralph
>Assignee: Su Ralph
>Priority: Minor
> Fix For: v0.5.1
>
>
> From Capital One case
> 
> It looks very interesting that Postgres has this behavior. Is Postgres your 
> production setting for holding hive metadata?
> If that is the case, I think we need extend Eagle a little bit to support 
> Postgres. (Hive metadata tables use upper case for both table name and column 
> name)
> Thanks
> Edward
> On Mon, Apr 11, 2016 at 9:02 PM, Carnali, Matthew R. 
>  wrote:
> Here are the correct queries:
> 1.
> select "NAME" from "DBS”;
> 2. 
> select "t"."TBL_NAME" from "TBLS" t, "DBS" d where "t"."DB_ID"="d"."DB_ID" 
> and "d"."NAME"='%s’;
> 3.
> select "c"."COLUMN_NAME" from "DBS" d join "TBLS" t on 
> "d"."DB_ID"="t"."DB_ID" join "SDS" s on "t"."SD_ID"="s"."SD_ID" join 
> "COLUMNS_V2" c on "s"."CD_ID"="c"."CD_ID" where "d"."NAME"='%s' and 
> "t"."TBL_NAME"='%s';
> From: "Carnali, Matthew R." 
> Date: Monday, April 11, 2016 at 8:11 PM
> To: Edward Zhang 
> Cc: "qingwz...@ebay.com" , Hao Chen , 
> "li...@ebay.com" 
> Subject: Re: Fail to get WEB_CONFIG configurations for data classification
> So what I found is the following:
> http://stackoverflow.com/questions/6331504/omitting-the-double-quote-to-do-query-on-postgresql
> I modified the queries to have quotes like so (but it still does not seem 
> like it is working correctly, I am investigating further):
> 1. select ’NAME' from "DBS";
> 2. select 't.TBL_NAME' from "TBLS" t, "DBS" d where 't.db_id'='d.db_id' and 
> 'd.name'='%s’;
> 3. select 'c.column_name' from "DBS" d join "TBLS" t on 'd.db_id'='t.db_id' 
> join "SDS" s on 't.sd_id'='s.sd_id' join "COLUMNS_V2" c on 
> 's.cd_id'='c.cd_id' where 'd.name'='%s' and 't.tbl_name'='%s’;
> From: Edward Zhang 
> Date: Monday, April 11, 2016 at 3:52 PM
> To: "Carnali, Matthew R." 
> Cc: "qingwz...@ebay.com" , Hao Chen , 
> "li...@ebay.com" 
> Subject: Re: Fail to get WEB_CONFIG configurations for data classification
> We use the following queries, let me know if any of queries can't be run 
> directly against postgres?
> 1. to get databases
> String sql = "select name from DBS";
> 2. to get tables
> String sql_format = "select t.tbl_name from TBLS t, DBS d where 
> t.db_id=d.db_id and d.name='%s'";
> 3. to get columns
> String sql_format =
> "select c.column_name " +
> "from DBS d join TBLS t on d.db_id=t.db_id " +
> "join SDS s on t.sd_id=s.sd_id " +
> "join COLUMNS_V2 c on s.cd_id=c.cd_id " +
> "where d.name='%s' and t.tbl_name='%s';";



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-1004) Test branch-0.5 with apps on Dev/Staging environment

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-1004:
--
Fix Version/s: (was: v0.5.0)
   v0.5.1

> Test branch-0.5 with apps on Dev/Staging environment
> 
>
> Key: EAGLE-1004
> URL: https://issues.apache.org/jira/browse/EAGLE-1004
> Project: Eagle
>  Issue Type: Sub-task
>Reporter: Jayesh
> Fix For: v0.5.1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (EAGLE-360) Kafka Java Producer with kerberos

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-360.
--
   Resolution: Won't Fix
Fix Version/s: (was: v0.6.0)
   v0.5.0

oh ok, Thanks for confirming.

> Kafka Java Producer with kerberos
> -
>
> Key: EAGLE-360
> URL: https://issues.apache.org/jira/browse/EAGLE-360
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: DanielZhou
> Fix For: v0.5.0
>
>
> *log4j.properties*
> {code}
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityProtocol=PLAINTEXTSASL
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityKrb5Conf=/etc/krb5.conf
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityAuthLoginConfig=/etc/kafka/kafka_jaas.conf
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityAuthUseSubjectCredsOnly=false
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityKrb5Debug=true
> {code}
> *kafka_jaas.conf*
> {code}
> KafkaClient {
> com.sun.security.auth.module.Krb5LoginModule required
> doNotPrompt=true
> useTicketCache=true
> principal="ctad...@eagle.incubator.apache.org"
> useKeyTab=true
> serviceName="kafka"
> keyTab="/etc/security/keytabs/ctadmin.keytab"
> client=true;
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (EAGLE-525) refactor oozie to new application framework

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-525.
--
Resolution: Fixed

> refactor oozie to new application framework
> ---
>
> Key: EAGLE-525
> URL: https://issues.apache.org/jira/browse/EAGLE-525
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: juhe
>Assignee: juhe
>Priority: Minor
> Fix For: v0.5.0
>
>
> h2. Main Changes
> * Modify kafka spout schema to StringScheme
> * Modify for oozie restful service
> * Filter the abnormal oozie message in oozie parser



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-360) Kafka Java Producer with kerberos

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-360:
-
Fix Version/s: (was: v0.5.0)

> Kafka Java Producer with kerberos
> -
>
> Key: EAGLE-360
> URL: https://issues.apache.org/jira/browse/EAGLE-360
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: DanielZhou
> Fix For: v0.6.0
>
>
> *log4j.properties*
> {code}
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityProtocol=PLAINTEXTSASL
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityKrb5Conf=/etc/krb5.conf
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityAuthLoginConfig=/etc/kafka/kafka_jaas.conf
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityAuthUseSubjectCredsOnly=false
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityKrb5Debug=true
> {code}
> *kafka_jaas.conf*
> {code}
> KafkaClient {
> com.sun.security.auth.module.Krb5LoginModule required
> doNotPrompt=true
> useTicketCache=true
> principal="ctad...@eagle.incubator.apache.org"
> useKeyTab=true
> serviceName="kafka"
> keyTab="/etc/security/keytabs/ctadmin.keytab"
> client=true;
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (EAGLE-360) Kafka Java Producer with kerberos

[Jayesh (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16084473#comment-16084473
 ] 

Jayesh commented on EAGLE-360:
--

[~DanielZhou], was this tested ?

> Kafka Java Producer with kerberos
> -
>
> Key: EAGLE-360
> URL: https://issues.apache.org/jira/browse/EAGLE-360
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: DanielZhou
> Fix For: v0.6.0
>
>
> *log4j.properties*
> {code}
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityProtocol=PLAINTEXTSASL
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityKrb5Conf=/etc/krb5.conf
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityAuthLoginConfig=/etc/kafka/kafka_jaas.conf
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityAuthUseSubjectCredsOnly=false
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityKrb5Debug=true
> {code}
> *kafka_jaas.conf*
> {code}
> KafkaClient {
> com.sun.security.auth.module.Krb5LoginModule required
> doNotPrompt=true
> useTicketCache=true
> principal="ctad...@eagle.incubator.apache.org"
> useKeyTab=true
> serviceName="kafka"
> keyTab="/etc/security/keytabs/ctadmin.keytab"
> client=true;
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-360) Kafka Java Producer with kerberos

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-360:
-
Fix Version/s: (was: v0.4.1)
   v0.6.0

> Kafka Java Producer with kerberos
> -
>
> Key: EAGLE-360
> URL: https://issues.apache.org/jira/browse/EAGLE-360
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: DanielZhou
> Fix For: v0.6.0
>
>
> *log4j.properties*
> {code}
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityProtocol=PLAINTEXTSASL
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityKrb5Conf=/etc/krb5.conf
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityAuthLoginConfig=/etc/kafka/kafka_jaas.conf
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityAuthUseSubjectCredsOnly=false
> log4j.appender.KAFKA_HDFS_AUDIT.SecurityKrb5Debug=true
> {code}
> *kafka_jaas.conf*
> {code}
> KafkaClient {
> com.sun.security.auth.module.Krb5LoginModule required
> doNotPrompt=true
> useTicketCache=true
> principal="ctad...@eagle.incubator.apache.org"
> useKeyTab=true
> serviceName="kafka"
> keyTab="/etc/security/keytabs/ctadmin.keytab"
> client=true;
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (EAGLE-1057) use openjdk instead of oracle jdk

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-1057.
---
Resolution: Fixed

> use openjdk instead of oracle jdk
> -
>
> Key: EAGLE-1057
> URL: https://issues.apache.org/jira/browse/EAGLE-1057
> Project: Eagle
>  Issue Type: Sub-task
>  Components: Integration::Docker
>Reporter: Jayesh
>Assignee: Jayesh
>Priority: Minor
> Fix For: v0.5.0
>
>
> oracle jdk download is not reliable, we can use openjdk instead



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (EAGLE-925) Eagle Docker Image for v0.5

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-925.
--
Resolution: Fixed

> Eagle Docker Image for v0.5
> ---
>
> Key: EAGLE-925
> URL: https://issues.apache.org/jira/browse/EAGLE-925
> Project: Eagle
>  Issue Type: New Feature
>  Components: Integration::Docker
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Jayesh
> Fix For: v0.5.0
>
>  Time Spent: 328h
>  Remaining Estimate: 0h
>
> As we do a lot of refactor for v0.5 so we need to create a new Eagle Docker 
> for v0.5, referring to 
> https://github.com/apache/eagle/tree/branch-0.4/eagle-external/eagle-docker 
> which is out of date.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (EAGLE-1006) Fix memory leak issue in eagle server

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-1006.
---
Resolution: Fixed

> Fix memory leak issue in eagle server
> -
>
> Key: EAGLE-1006
> URL: https://issues.apache.org/jira/browse/EAGLE-1006
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> After eagle server started for a long time, the response time will be very 
> slow to user request and the memory usage is very large. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (EAGLE-1023) update Hadoop jmx metric collector scripts & fix bugs

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-1023:
--
Fix Version/s: v0.5.0

> update Hadoop jmx metric collector scripts & fix bugs
> -
>
> Key: EAGLE-1023
> URL: https://issues.apache.org/jira/browse/EAGLE-1023
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> update Hadoop jmx metric collector scripts



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (EAGLE-1023) update Hadoop jmx metric collector scripts & fix bugs

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-1023.
---
Resolution: Fixed

> update Hadoop jmx metric collector scripts & fix bugs
> -
>
> Key: EAGLE-1023
> URL: https://issues.apache.org/jira/browse/EAGLE-1023
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> update Hadoop jmx metric collector scripts



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (EAGLE-1030) Unknown column 'eaglejpa_process_process.site' in 'field list' - using JDBC

[Jayesh (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036154#comment-16036154
 ] 

Jayesh commented on EAGLE-1030:
---

[~r7raul], is adding site in table eaglejpa_process_process, the right way to 
fix this issue ?

> Unknown column 'eaglejpa_process_process.site' in 'field list' - using JDBC
> ---
>
> Key: EAGLE-1030
> URL: https://issues.apache.org/jira/browse/EAGLE-1030
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
> Environment: Cent 0S 6.8
> MySQL Community Server (GPL) 5.7.18
> x86_64 for linux
> eagle 0.5
> hadoop 2.6.4
>Reporter: Alexandre
>
> Hi,
> I'm using JDBC for apache eagle and i have this exception in 
> "log/eagle-server.log": 
> ERROR [2017-06-02 08:02:45,403] org.apache.eagle.storage.jdbc.JdbcStorage: 
> Failed to query by: SELECT max(eaglejpa_process_process.currentTimeStamp), 
> eaglejpa_process_process.site FROM eaglejpa_process_process WHERE 
> (eaglejpa_process_process.timestamp>=? AND 
> eaglejpa_process_process.timestamp GROUP BY eaglejpa_process_process.site LIMIT 10 Replacements: 
> [1493798565000,1496390565000,site1]
> ! com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 
> 'eaglejpa_process_process.site' in 'field list'
> ! at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 
> ~[na:1.8.0_31]
> ! at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>  ~[na:1.8.0_31]
> ! at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>  ~[na:1.8.0_31]
> ! at java.lang.reflect.Constructor.newInstance(Constructor.java:408) 
> ~[na:1.8.0_31]
> ! at com.mysql.jdbc.Util.handleNewInstance(Util.java:377) 
> ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at com.mysql.jdbc.Util.getInstance(Util.java:360) 
> ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:978) 
> ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3887) 
> ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3823) 
> ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435) 
> ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582) 
> ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2530) 
> ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1907) 
> ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2030) 
> ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
>  ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at org.apache.torque.util.BasePeerImpl.doSelect(BasePeerImpl.java:1535) 
> ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! ... 61 common frames omitted
> ! Causing: org.apache.torque.TorqueException: 
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 
> 'eaglejpa_process_process.site' in 'field list'
> ! at 
> org.apache.torque.util.ExceptionMapperImpl.toTorqueException(ExceptionMapperImpl.java:59)
>  ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at org.apache.torque.util.BasePeerImpl.doSelect(BasePeerImpl.java:1608) 
> ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at org.apache.torque.util.BasePeerImpl.doSelect(BasePeerImpl.java:1152) 
> ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.storage.jdbc.entity.impl.JdbcEntityReaderImpl.query(JdbcEntityReaderImpl.java:75)
>  ~[eagle-storage-jdbc-0.5.0-SNAPSHOT.jar:0.5.0-SNAPSHOT]
> ! ... 59 common frames omitted
> ! Causing: java.io.IOException: Failed to query by: SELECT 
> max(eaglejpa_process_process.currentTimeStamp), eaglejpa_process_process.site 
> FROM eaglejpa_process_process WHERE (eaglejpa_process_process.timestamp>=? 
> AND eaglejpa_process_process.timestamp GROUP BY eaglejpa_process_process.site LIMIT 10 Replacements: 
> [1493798565000,1496390565000,site1]
> ! at 
> org.apache.eagle.storage.jdbc.entity.impl.JdbcEntityReaderImpl.query(JdbcEntityReaderImpl.java:82)
>  ~[eagle-storage-jdbc-0.5.0-SNAPSHOT.jar:0.5.0-SNAPSHOT]
> ! at org.apache.eagle.storage.jdbc.JdbcStorage.query(JdbcStorage.java:161) 
> ~[eagle-storage-jdbc-0.5.0-SNAPSHOT.jar:0.5.0-SNAPSHOT]
> ! at 
> org.apache.eagle.storage.operation.QueryStatement.execute(QueryStatement.java:47)
>  

[jira] [Commented] (EAGLE-968) using Email Notification Feature throws IncompatibleClassChangeError

[Jayesh (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020015#comment-16020015
 ] 

Jayesh commented on EAGLE-968:
--

anyway, this issue affects the new storm version which is targeted for eagle 
0.6.

> using Email Notification Feature throws IncompatibleClassChangeError
> 
>
> Key: EAGLE-968
> URL: https://issues.apache.org/jira/browse/EAGLE-968
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Jayesh
>Assignee: Jayesh
> Fix For: v0.6.0
>
>
> {code}
> 2017-03-19 20:42:56.369 o.a.e.a.e.p.e.AlertEmailGenerator 
> Thread-46-alertPublishBolt-executor[17 17] [ERROR] Failed to send email to 
> @gmail.com,@gmail.com, due 
> to:java.util.concurrent.ExecutionException: 
> java.lang.IncompatibleClassChangeError: Implementing class
> java.util.concurrent.ExecutionException: 
> java.lang.IncompatibleClassChangeError: Implementing class
>   at java.util.concurrent.FutureTask.report(FutureTask.java:122) 
> ~[?:1.8.0_102]
>   at java.util.concurrent.FutureTask.get(FutureTask.java:206) 
> ~[?:1.8.0_102]
>   at 
> org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:89)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:55)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertEmailPublisher.onAlert(AlertEmailPublisher.java:130)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:88)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.nextEvent(AlertPublisherImpl.java:70)
>  [stormjar.jar:?]
>   at 
> org.apache.eagle.alert.engine.runner.AlertPublisherBolt.execute(AlertPublisherBolt.java:92)
>  [stormjar.jar:?]
>   at 
> org.apache.storm.daemon.executor$fn__4973$tuple_action_fn__4975.invoke(executor.clj:727)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.daemon.executor$mk_task_receiver$fn__4894.invoke(executor.clj:459)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.disruptor$clojure_handler$reify__4409.onEvent(disruptor.clj:40)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:453)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:432)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:73)
>  [storm-core-1.0.3.jar:1.0.3]
>   at 
> org.apache.storm.daemon.executor$fn__4973$fn__4986$fn__5039.invoke(executor.clj:846)
>  [storm-core-1.0.3.jar:1.0.3]
>   at org.apache.storm.util$async_loop$fn__557.invoke(util.clj:484) 
> [storm-core-1.0.3.jar:1.0.3]
>   at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?]
>   at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102]
> Caused by: java.lang.IncompatibleClassChangeError: Implementing class
>   at java.lang.ClassLoader.defineClass1(Native Method) ~[?:1.8.0_102]
>   at java.lang.ClassLoader.defineClass(ClassLoader.java:763) 
> ~[?:1.8.0_102]
>   at 
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) 
> ~[?:1.8.0_102]
>   at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) 
> ~[?:1.8.0_102]
>   at java.net.URLClassLoader.access$100(URLClassLoader.java:73) 
> ~[?:1.8.0_102]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:368) ~[?:1.8.0_102]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:362) ~[?:1.8.0_102]
>   at java.security.AccessController.doPrivileged(Native Method) 
> ~[?:1.8.0_102]
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:361) 
> ~[?:1.8.0_102]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_102]
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) 
> ~[?:1.8.0_102]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_102]
>   at 
> org.apache.velocity.runtime.log.Log4JLogChute.initAppender(Log4JLogChute.java:118)
>  ~[stormjar.jar:?]
>   at 
> org.apache.velocity.runtime.log.Log4JLogChute.init(Log4JLogChute.java:85) 
> ~[stormjar.jar:?]
>   at 
> org.apache.velocity.runtime.log.LogManager.createLogChute(LogManager.java:157)
>  ~[stormjar.jar:?]
>   at 
> org.apache.velocity.runtime.log.LogManager.updateLog(LogManager.java:269) 
> ~[stormjar.jar:?]
>   at 
> org.apache.velocity.runtime.RuntimeInstance.initializeLog(RuntimeInstance.java:871)
>  ~[stormjar.jar:?]
>   at 
> 

[jira] [Created] (EAGLE-1025) bump version on master

[Jayesh (JIRA)]

Jayesh created EAGLE-1025:
-

 Summary: bump version on master
 Key: EAGLE-1025
 URL: https://issues.apache.org/jira/browse/EAGLE-1025
 Project: Eagle
  Issue Type: Sub-task
Reporter: Jayesh
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-463) One App type may be run as multiple instances in one site

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-463:
-
Fix Version/s: (was: v0.5.0)
   v0.6.0

> One App type may be run as multiple instances in one site
> -
>
> Key: EAGLE-463
> URL: https://issues.apache.org/jira/browse/EAGLE-463
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.6.0
>
>
> Today in one site, one app type can be run only as one instance. In some 
> scenarios, one application code can be run with multiple instances, for 
> example to deal with different topics.
> One typical example is JMX metric application can be for namenode, datanode , 
> resource manager etc. They are all the same type of applications, i.e. code 
> logic with different configurations for example topic for data sources



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (EAGLE-965) Eagle JPM Yarn Overview Chart Improvement

[Jayesh (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003983#comment-16003983
 ] 

Jayesh commented on EAGLE-965:
--

Hi [~smith3816], are you working on this, do you think we can include this in 
0.5 ?

> Eagle JPM Yarn Overview Chart Improvement
> -
>
> Key: EAGLE-965
> URL: https://issues.apache.org/jira/browse/EAGLE-965
> Project: Eagle
>  Issue Type: Bug
>  Components: App::Job Performance Monitor
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Jilin, Jiang
> Fix For: v0.5.0
>
>
> 1. Fix CPU Usage Unit/IO OPS on "Yarn Jobs/Overview" page, currently use 
> storage unit
> 2. Add chart legend and description under the chart about:
> 1) How Top-N is calculated and sorted?
> 2) Explain data point's value is 0?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (EAGLE-1006) Memory leak in Eagle Server

[Jayesh (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003757#comment-16003757
 ] 

Jayesh commented on EAGLE-1006:
---

Hi [~qingwzhao], do you think all the possible memory leaks has been 
identified? and we can close this ticket with the current fix? or we should 
keep this open ?

> Memory leak in Eagle Server
> ---
>
> Key: EAGLE-1006
> URL: https://issues.apache.org/jira/browse/EAGLE-1006
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> After eagle server started for a long time, the response time will be very 
> slow to user request and the memory usage is very large. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-652) services health check for hdfs,hbase and yarn

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-652.
--
Resolution: Fixed

> services health check for hdfs,hbase and yarn
> -
>
> Key: EAGLE-652
> URL: https://issues.apache.org/jira/browse/EAGLE-652
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
> Fix For: v0.5.0
>
>
> The app aims to monitor those services with a master-slave structured 
> topology, and provides metrics at the HOST level. Specifically, this app will 
> support the following services healthy check
> •HDFS: namenode, datanode, journalnode
> •HBASE: hmaster, regionservers
> YARN: resourcemanager, nodemanagers, historyserver



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-652) services health check for hdfs,hbase and yarn

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-652:
-
Fix Version/s: v0.5.0

> services health check for hdfs,hbase and yarn
> -
>
> Key: EAGLE-652
> URL: https://issues.apache.org/jira/browse/EAGLE-652
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
> Fix For: v0.5.0
>
>
> The app aims to monitor those services with a master-slave structured 
> topology, and provides metrics at the HOST level. Specifically, this app will 
> support the following services healthy check
> •HDFS: namenode, datanode, journalnode
> •HBASE: hmaster, regionservers
> YARN: resourcemanager, nodemanagers, historyserver



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-729) add hbase kerberose principle and keytab to provider

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-729.
--
Resolution: Fixed

> add hbase kerberose principle and keytab to provider
> 
>
> Key: EAGLE-729
> URL: https://issues.apache.org/jira/browse/EAGLE-729
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
> Fix For: v0.5.0
>
>
> Add hbase kerberose principle and keytab to provider xml file



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-766) Set default host of JPM_WEB_APP as null

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-766.
--
Resolution: Fixed

> Set default host of JPM_WEB_APP as null
> 
>
> Key: EAGLE-766
> URL: https://issues.apache.org/jira/browse/EAGLE-766
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Set default host & port of JPM_WEB_APP as N/A to make sure the web will read 
> web service from configured instead of always using current.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-807) Refactor JMX Metric Collector Script

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-807.
--
Resolution: Fixed

> Refactor JMX Metric Collector Script
> 
>
> Key: EAGLE-807
> URL: https://issues.apache.org/jira/browse/EAGLE-807
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Refactor JMX Metric Collector Script
> * Support multiple kafka topics
> * Support HA checking logic.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-789) Add a new publisher to write alerts into a local file

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-789.
--
Resolution: Fixed

> Add a new publisher to write alerts into a local file
> -
>
> Key: EAGLE-789
> URL: https://issues.apache.org/jira/browse/EAGLE-789
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> Add a new publisher to write alerts into a local file
> configuration:
> {
>"fileName" : "/tmp/eagle-alert.log",
>"rotate_every_kb": 1024,
>"number_of_files": 1
> }
> Result sample:
> Nov 18, 2016 6:05:14 PM 
> org.apache.eagle.alert.engine.publisher.impl.AlertFilePublisher onAlert
> INFO: 2016-11-18 10:05:14 UTC alertId=058269d2-f301-4e66-b924-3ea8cf577fc5, 
> siteId=sandbox, policyId=test, alertData={securityZone=NA, 
> dst=/user/hdfs/.Trash/Current/tmp/test/subtest/private1479463504173, 
> sensitivityType=NA, src=/tmp/test/subtest/private, allowed=true, 
> host=10.249.66.185, cmd=rename, user=hdfs, timestamp=1479463504177}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-806) Integrate Metric Process and Persistence with Application Framework

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-806.
--
Resolution: Fixed

> Integrate Metric Process and Persistence with Application Framework
> ---
>
> Key: EAGLE-806
> URL: https://issues.apache.org/jira/browse/EAGLE-806
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Integrate Stream Source and Metric Persistence with Application Framework
> * Provide API to easily ingest, process, aggregate and persist metric
> * Integrate stream source
> * Integrate metric definition and metric persistence.
> * Implement basic plug-able aggregation abstraction for later usage.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-785) change hbase configuration to optional

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-785.
--
Resolution: Fixed

> change hbase configuration to optional
> --
>
> Key: EAGLE-785
> URL: https://issues.apache.org/jira/browse/EAGLE-785
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
> Fix For: v0.5.0
>
>
> change hbase configuration to optional as artemis and ares do not have hbase



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-508) Fix NullPointerException when zookeeper is trying to shutdown in ZookeeperEmbedded.

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-508.
--
Resolution: Fixed

> Fix NullPointerException when zookeeper is trying to shutdown in 
> ZookeeperEmbedded.
> ---
>
> Key: EAGLE-508
> URL: https://issues.apache.org/jira/browse/EAGLE-508
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Huizhi Lu
>Assignee: Huizhi Lu
> Fix For: v0.5.0
>
>
> Root cause: zookeeper.getState() may be null so zookeeper.getState().equals() 
> would throw NullPointerException.
> Solution: CuratorFrameworkState.STOPPED.equals(zookeeper.getState())
> ---
>  T E S T S
> ---
> Running com.apache.eagle.service.app.TestServiceAppWithZk
> java.lang.NullPointerException
>   at 
> org.apache.eagle.alert.utils.ZookeeperEmbedded.shutdown(ZookeeperEmbedded.java:55)
>   at 
> com.apache.eagle.service.app.TestServiceAppWithZk.tearDown(TestServiceAppWithZk.java:76)
>   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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59)
>   at 
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:120)
>   at 
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:103)
>   at org.apache.maven.surefire.Surefire.run(Surefire.java:169)
>   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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350)
>   at 
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021)
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 3.231 sec <<< 
> FAILURE!
> Results :
> Tests in error: 
>   testMain(com.apache.eagle.service.app.TestServiceAppWithZk)
>   testMain(com.apache.eagle.service.app.TestServiceAppWithZk)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-915) Fetch accepted MR jobs to assist queue analysis

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-915.
--
Resolution: Fixed

> Fetch accepted MR jobs to assist queue analysis
> ---
>
> Key: EAGLE-915
> URL: https://issues.apache.org/jira/browse/EAGLE-915
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> If a job is in accepted state for a long time, the submitted queue is 
> considered unhealthy



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-915) Fetch accepted MR jobs to assist queue analysis

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-915:
-
Fix Version/s: v0.5.0

> Fetch accepted MR jobs to assist queue analysis
> ---
>
> Key: EAGLE-915
> URL: https://issues.apache.org/jira/browse/EAGLE-915
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> If a job is in accepted state for a long time, the submitted queue is 
> considered unhealthy



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-843) Refactor application shared service registry framework

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-843.
--
Resolution: Fixed

> Refactor application shared service registry framework
> --
>
> Key: EAGLE-843
> URL: https://issues.apache.org/jira/browse/EAGLE-843
> Project: Eagle
>  Issue Type: Improvement
>  Components: Core::App Engine
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: eagle-framework
> Fix For: v0.5.0
>
>
> Refactor application shared service registry framework:
> * Add `Optional getSharedServices(Config envConfig)` in 
> `ApplicationProvider`
> * Move `MRHistoryJobDailyReporter` registry to 
> `MRHistoryJobApplicationProvider` from `ServerApplication`
> * Register `getSharedServices` from `ApplicationProvider` to `Environment` in 
> `ServerApplication`
> https://issues.apache.org/jira/browse/EAGLE-843



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-869) Fix MetricStreamPersist bug: no tuple pass on when batchSize > 1

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-869.
--
Resolution: Fixed

> Fix MetricStreamPersist bug: no tuple pass on when batchSize > 1
> 
>
> Key: EAGLE-869
> URL: https://issues.apache.org/jira/browse/EAGLE-869
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Fix MetricStreamPersist bug: no tuple pass on when batchSize > 1



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-895) Improve alert engine metadata to organize by siteId

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-895.
--
Resolution: Fixed

> Improve alert engine metadata to organize by siteId 
> 
>
> Key: EAGLE-895
> URL: https://issues.apache.org/jira/browse/EAGLE-895
> Project: Eagle
>  Issue Type: Improvement
>  Components: Core::Alert Engine
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Improve alert engine metadata to organize by siteId 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-1008) java.lang.NullPointerException in JHFEventReaderBase.close

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-1008:
--
Fix Version/s: v0.5.0

> 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
> Fix For: v0.5.0
>
>
> {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)

[jira] [Resolved] (EAGLE-1008) java.lang.NullPointerException in JHFEventReaderBase.close

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-1008.
---
Resolution: Fixed

> 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
> Fix For: v0.5.0
>
>
> {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)

[jira] [Resolved] (EAGLE-971) Duplicated queues are generated under a monitored stream

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-971.
--
Resolution: Fixed

> Duplicated queues are generated under a monitored stream
> 
>
> Key: EAGLE-971
> URL: https://issues.apache.org/jira/browse/EAGLE-971
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> This issue is caused by the wrong routing spec generated by the coordinator. 
> Here is the procedure to reproduce it. 
> 1. setting {{policiesPerBolt = 2, streamsPerBolt = 3, reuseBoltInStreams = 
> true}} in server config
> 2. create four policies which has the same partition and consume the same 
> stream
> {code}
>  from HADOOP_JMX_METRIC_STREAM_SANDBOX[metric == 
> "hadoop.namenode.rpc.callqueuelength"]#window.length(2) select site, host, 
> component, metric, min(convert(value, "long")) as minValue group by site, 
> host, component, metric having minValue >= 1 insert into 
> HADOOP_JMX_METRIC_STREAM_SANDBOX_CALL_QUEUE_EXCEEDS_OUT;
> from HADOOP_JMX_METRIC_STREAM_SANDBOX[metric == 
> "hadoop.namenode.rpc.callqueuelength"]#window.length(30) select site, host, 
> component, metric, min(convert(value, "long")) as minValue group by site, 
> host, component, metric having minValue >= 1 insert into 
> HADOOP_JMX_METRIC_STREAM_SANDBOX_CALL_QUEUE_EXCEEDS_OUT;
> from HADOOP_JMX_METRIC_STREAM_SANDBOX[metric == 
> "hadoop.namenode.hastate.failed.count"]#window.length(2) select site, host, 
> component, metric, timestamp, min(value) as minValue group by site, host, 
> component, metric insert into 
> HADOOP_JMX_METRIC_STREAM_SANDBOX_NN_NO_RESPONSE_OUT
> from HADOOP_JMX_METRIC_STREAM_SANDBOX[metric == 
> "hadoop.namenode.hastate.failed.count.test"]#window.length(3) select site, 
> host, component, metric, count(value) as cnt group by site, host, component, 
> metric insert into HADOOP_JMX_METRIC_STREAM_SANDBOX_NN_NO_RESPONSE_OUT;
> {code}
> After creating the four policies, the routing spec is 
> {code}
> routerSpecs: [
> {
> streamId: "HADOOP_JMX_METRIC_STREAM_SANDBOX",
> partition: {
> streamId: "HADOOP_JMX_METRIC_STREAM_SANDBOX",
> type: "GROUPBY",
> columns: [
> "site",
> "host",
> "component",
> "metric"
> ],
> sortSpec: null
> },
> targetQueue: [
> {
> partition: {
> streamId: "HADOOP_JMX_METRIC_STREAM_SANDBOX",
> type: "GROUPBY",
> columns: [
> "site",
> "host",
> "component",
> "metric"
> ],
> sortSpec: null
> },
> workers: [
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt9"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt0"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt1"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt2"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt3"
> }
> ]
> },
> {
> partition: {
> streamId: "HADOOP_JMX_METRIC_STREAM_SANDBOX",
> type: "GROUPBY",
> columns: [
> "site",
> "host",
> "component",
> "metric"
> ],
> sortSpec: null
> },
> workers: [
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt9"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt0"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt1"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt2"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt3"
> }
> ]
> },
> {
> partition: {
> streamId: "HADOOP_JMX_METRIC_STREAM_SANDBOX",
> type: "GROUPBY",
> columns: [
> "site",
> "host",
> "component",
> "metric"
> ],
> sortSpec: null
> },
> workers: [
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt9"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt0"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt1"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt2"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt3"
> }
> ]
> }
> ]
> }
> ]
> {code}
> and the alert spec is 
> {code}
> boltPolicyIdsMap: {
> alertBolt9: [
> "NameNodeWithOneNoResponse",
> "NameNodeHAHasNoResponse",
> "CallQueueLengthExceeds30Times",
> "CallQueueLengthExceeds2Times"
> ],
> alertBolt0: [
> "NameNodeWithOneNoResponse",
> "NameNodeHAHasNoResponse",
> "CallQueueLengthExceeds30Times",
> "CallQueueLengthExceeds2Times"
> ],
> alertBolt1: [
> "NameNodeWithOneNoResponse",
> "NameNodeHAHasNoResponse",
> "CallQueueLengthExceeds30Times",
> "CallQueueLengthExceeds2Times"
> ],
> alertBolt2: [
> "NameNodeWithOneNoResponse",
> "NameNodeHAHasNoResponse",
> "CallQueueLengthExceeds30Times",
> 

[jira] [Updated] (EAGLE-971) Duplicated queues are generated under a monitored stream

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-971:
-
Fix Version/s: v0.5.0

> Duplicated queues are generated under a monitored stream
> 
>
> Key: EAGLE-971
> URL: https://issues.apache.org/jira/browse/EAGLE-971
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> This issue is caused by the wrong routing spec generated by the coordinator. 
> Here is the procedure to reproduce it. 
> 1. setting {{policiesPerBolt = 2, streamsPerBolt = 3, reuseBoltInStreams = 
> true}} in server config
> 2. create four policies which has the same partition and consume the same 
> stream
> {code}
>  from HADOOP_JMX_METRIC_STREAM_SANDBOX[metric == 
> "hadoop.namenode.rpc.callqueuelength"]#window.length(2) select site, host, 
> component, metric, min(convert(value, "long")) as minValue group by site, 
> host, component, metric having minValue >= 1 insert into 
> HADOOP_JMX_METRIC_STREAM_SANDBOX_CALL_QUEUE_EXCEEDS_OUT;
> from HADOOP_JMX_METRIC_STREAM_SANDBOX[metric == 
> "hadoop.namenode.rpc.callqueuelength"]#window.length(30) select site, host, 
> component, metric, min(convert(value, "long")) as minValue group by site, 
> host, component, metric having minValue >= 1 insert into 
> HADOOP_JMX_METRIC_STREAM_SANDBOX_CALL_QUEUE_EXCEEDS_OUT;
> from HADOOP_JMX_METRIC_STREAM_SANDBOX[metric == 
> "hadoop.namenode.hastate.failed.count"]#window.length(2) select site, host, 
> component, metric, timestamp, min(value) as minValue group by site, host, 
> component, metric insert into 
> HADOOP_JMX_METRIC_STREAM_SANDBOX_NN_NO_RESPONSE_OUT
> from HADOOP_JMX_METRIC_STREAM_SANDBOX[metric == 
> "hadoop.namenode.hastate.failed.count.test"]#window.length(3) select site, 
> host, component, metric, count(value) as cnt group by site, host, component, 
> metric insert into HADOOP_JMX_METRIC_STREAM_SANDBOX_NN_NO_RESPONSE_OUT;
> {code}
> After creating the four policies, the routing spec is 
> {code}
> routerSpecs: [
> {
> streamId: "HADOOP_JMX_METRIC_STREAM_SANDBOX",
> partition: {
> streamId: "HADOOP_JMX_METRIC_STREAM_SANDBOX",
> type: "GROUPBY",
> columns: [
> "site",
> "host",
> "component",
> "metric"
> ],
> sortSpec: null
> },
> targetQueue: [
> {
> partition: {
> streamId: "HADOOP_JMX_METRIC_STREAM_SANDBOX",
> type: "GROUPBY",
> columns: [
> "site",
> "host",
> "component",
> "metric"
> ],
> sortSpec: null
> },
> workers: [
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt9"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt0"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt1"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt2"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt3"
> }
> ]
> },
> {
> partition: {
> streamId: "HADOOP_JMX_METRIC_STREAM_SANDBOX",
> type: "GROUPBY",
> columns: [
> "site",
> "host",
> "component",
> "metric"
> ],
> sortSpec: null
> },
> workers: [
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt9"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt0"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt1"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt2"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt3"
> }
> ]
> },
> {
> partition: {
> streamId: "HADOOP_JMX_METRIC_STREAM_SANDBOX",
> type: "GROUPBY",
> columns: [
> "site",
> "host",
> "component",
> "metric"
> ],
> sortSpec: null
> },
> workers: [
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt9"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt0"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt1"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt2"
> },
> {
> topologyName: "ALERT_UNIT_TOPOLOGY_APP_SANDBOX",
> boltId: "alertBolt3"
> }
> ]
> }
> ]
> }
> ]
> {code}
> and the alert spec is 
> {code}
> boltPolicyIdsMap: {
> alertBolt9: [
> "NameNodeWithOneNoResponse",
> "NameNodeHAHasNoResponse",
> "CallQueueLengthExceeds30Times",
> "CallQueueLengthExceeds2Times"
> ],
> alertBolt0: [
> "NameNodeWithOneNoResponse",
> "NameNodeHAHasNoResponse",
> "CallQueueLengthExceeds30Times",
> "CallQueueLengthExceeds2Times"
> ],
> alertBolt1: [
> "NameNodeWithOneNoResponse",
> "NameNodeHAHasNoResponse",
> "CallQueueLengthExceeds30Times",
> "CallQueueLengthExceeds2Times"
> ],
> alertBolt2: [
> "NameNodeWithOneNoResponse",
> "NameNodeHAHasNoResponse",
> "CallQueueLengthExceeds30Times",
> 

[jira] [Updated] (EAGLE-993) add duplicate removal settings in policy definition

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-993:
-
Fix Version/s: v0.5.0

> add duplicate removal settings in policy definition
> ---
>
> Key: EAGLE-993
> URL: https://issues.apache.org/jira/browse/EAGLE-993
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> customize duplicate fields & interval in each policy



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-940) Hdfs RPC monitoring for per cluster/user

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-940:
-
Fix Version/s: v0.5.0

> 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
> Fix For: v0.5.0
>
>
> 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]{*}=hadoop.hdfs.auditlog.1m.count=1000
> * the last 5 minutes statistics
> http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}=hadoop.hdfs.auditlog.5m.count=1000
> * the last 25 minutes statistics 
> http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}=hadoop.hdfs.auditlog.25m.count=1000



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-940) Hdfs RPC monitoring for per cluster/user

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-940.
--
Resolution: Fixed

> 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]{*}=hadoop.hdfs.auditlog.1m.count=1000
> * the last 5 minutes statistics
> http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}=hadoop.hdfs.auditlog.5m.count=1000
> * the last 25 minutes statistics 
> http://localhost:9090/rest/entities?query=GenericMetricService[@site=%22sandbox%22]{*}=hadoop.hdfs.auditlog.25m.count=1000



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-927) add jmx resource info to Hadoop JMX Monitor

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-927.
--
Resolution: Fixed

> 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)

[jira] [Updated] (EAGLE-978) Queue capacity exceeds 100% on Eagle queue page

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-978:
-
Fix Version/s: v0.5.0

> Queue capacity exceeds 100% on Eagle queue page 
> 
>
> Key: EAGLE-978
> URL: https://issues.apache.org/jira/browse/EAGLE-978
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> We note the queue capacity exceeds the 100% in some cases



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-946) Refactor MRRunningJobApp & HadoopQueueApp

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-946.
--
Resolution: Fixed

> 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
> Fix For: v0.5.0
>
>
> 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] [Resolved] (EAGLE-978) Queue capacity exceeds 100% on Eagle queue page

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-978.
--
Resolution: Fixed

> Queue capacity exceeds 100% on Eagle queue page 
> 
>
> Key: EAGLE-978
> URL: https://issues.apache.org/jira/browse/EAGLE-978
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> We note the queue capacity exceeds the 100% in some cases



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-977) Duplicated entities are generated by TopologyHealthCheckApp

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-977:
-
Fix Version/s: v0.5.0

> Duplicated entities are generated by TopologyHealthCheckApp
> ---
>
> Key: EAGLE-977
> URL: https://issues.apache.org/jira/browse/EAGLE-977
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> For those time insensitive entities, the query engine will by default sets 
> their time as '1970-01-02 00:00:00', which will varies with the timezone when 
> written to HBase. 
> So if we change the time zone in Eagle server setting, duplicated entities 
> will be produced. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-919) Fix mr history null pointer exception when counters are null

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-919.
--
Resolution: Fixed

> Fix mr history null pointer exception when counters are null
> 
>
> Key: EAGLE-919
> URL: https://issues.apache.org/jira/browse/EAGLE-919
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> Fix null pointer exception in mr history job parser when counters are null



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-919) Fix mr history null pointer exception when counters are null

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-919:
-
Fix Version/s: v0.5.0

> Fix mr history null pointer exception when counters are null
> 
>
> Key: EAGLE-919
> URL: https://issues.apache.org/jira/browse/EAGLE-919
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> Fix null pointer exception in mr history job parser when counters are null



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-977) Duplicated entities are generated by TopologyHealthCheckApp

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-977.
--
Resolution: Fixed

> Duplicated entities are generated by TopologyHealthCheckApp
> ---
>
> Key: EAGLE-977
> URL: https://issues.apache.org/jira/browse/EAGLE-977
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> For those time insensitive entities, the query engine will by default sets 
> their time as '1970-01-02 00:00:00', which will varies with the timezone when 
> written to HBase. 
> So if we change the time zone in Eagle server setting, duplicated entities 
> will be produced. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-946) Refactor MRRunningJobApp & HadoopQueueApp

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-946:
-
Fix Version/s: v0.5.0

> 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
> Fix For: v0.5.0
>
>
> 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] [Resolved] (EAGLE-999) JobConfigSerDeser fails to serialize/deserialize data with long string

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-999.
--
Resolution: Fixed

> JobConfigSerDeser fails to serialize/deserialize data with long string 
> ---
>
> Key: EAGLE-999
> URL: https://issues.apache.org/jira/browse/EAGLE-999
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> Sample configuration value:
> {code}
> INSERT OVERWRITE TABLE kylin_intermediate_KYLIN_HIVE_METRICS_QUERY_CUBE SELECT
> HIVE_METRICS_QUERY_CUBE.`CUBE_NAME`
> ,HIVE_METRICS_QUERY_CUBE.`SEGMENT_NAME`
> ,HIVE_METRICS_QUERY_CUBE.`CUBOID_SOURCE`
> ,HIVE_METRICS_QUERY_CUBE.`CUBOID_TARGET`
> ,HIVE_METRICS_QUERY_CUBE.`IF_MATCH`
> ,HIVE_METRICS_QUERY_CUBE.`IF_SUCCESS`
> ,HIVE_METRICS_QUERY_CUBE.`KYEAR_BEGIN_DATE`
> ,HIVE_METRICS_QUERY_CUBE.`KMONTH_BEGIN_DATE`
> ,HIVE_METRICS_QUERY_CUBE.`KWEEK_BEGIN_DATE`
> ,HIVE_METRICS_QUERY_CUBE.`KDAY_DATE`
> ,HIVE_METRICS_QUERY_CUBE.`WEIGHT_PER_HIT`
> ,HIVE_METRICS_QUERY_CUBE.`STORAGE_CALL_COUNT`
> ,HIVE_METRICS_QUERY_CUBE.`STORAGE_CALL_TIME_SUM`
> ,HIVE_METRICS_QUERY_CUBE.`STORAGE_CALL_TIME_MAX`
> ,HIVE_METRICS_QUERY_CUBE.`STORAGE_COUNT_SKIP`
> ,HIVE_METRICS_QUERY_CUBE.`STORAGE_SIZE_SCAN`
> ,HIVE_METRICS_QUERY_CUBE.`STORAGE_SIZE_RETURN`
> ,HIVE_METRICS_QUERY_CUBE.`STORAGE_SIZE_AGGREGATE_FILTER`
> ,HIVE_METRICS_QUERY_CUBE.`STORAGE_SIZE_AGGREGATE`
> FROM KYLIN.HIVE_METRICS_QUERY_CUBE as HIVE_METRICS_QUERY_CUBE
> WHERE (((HIVE_METRICS_QUERY_CUBE.KDAY_DATE = '2017-04-06' AND 
> HIVE_METRICS_QUERY_CUBE.KDAY_TIME >= '18:00:00') OR 
> (HIVE_METRICS_QUERY_CUBE.KDAY_DATE > '2017-04-06')) AND 
> ((HIVE_METRICS_QUERY_CUBE.KDAY_DATE = '2017-04-06' AND 
> HIVE_METRICS_QUERY_CUBE.KDAY_TIME < '20:00:00') OR 
> (HIVE_METRICS_QUERY_CUBE.KDAY_DATE < '2017-04-06')))
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-1007) Fix memory leak in ExecutionRuntimeManager

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-1007.
---
Resolution: Fixed

> Fix memory leak in ExecutionRuntimeManager
> --
>
> Key: EAGLE-1007
> URL: https://issues.apache.org/jira/browse/EAGLE-1007
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> Fix memory leak in ExecutionRuntimeManager
> As equal method is not overrided in {{AbstractEnvironment}}, below return 
> statement has never been executed.  
> {code}
> if (executionRuntimeCache.containsKey(environment)) {
> return executionRuntimeCache.get(environment);
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-953) Host-level Overview Heatmap Diagram for Topology Monitoring

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-953.
--
Resolution: Fixed

> Host-level Overview Heatmap Diagram for Topology Monitoring
> ---
>
> Key: EAGLE-953
> URL: https://issues.apache.org/jira/browse/EAGLE-953
> Project: Eagle
>  Issue Type: New Feature
>  Components: App::Hadoop JMX Monitor
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: luokun
> Fix For: v0.5.0
>
>
> As hadoop operation user, want a host-level Overview Heatmap diagram for 
> servers like hadoop nodes like NameNode/DataNode/RegionServer, so that we 
> could easily identity healthy/unhealthy overview status of the whole cluster:
> Features:
> 1) HDFS Heatmap (Namenode/DataNode) / HBase HeatMap (HMaster/HRegionServer)
> 2) Use red for unhealthy and green for healthy nodes
> 3) Support to  display more detail status/metrics while hovering on certain 
> node (we could continuously add highlighted metrics in the detail section)
> 4) Support easily switch from `HeatMap`/`List` view by icon buttons
> 5) We should make sure our diagram compatible and rich information if 
> possible instead of separate different information everywhere.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-1014) No data in alertEngineSpout - handle exception

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-1014.
---
Resolution: Fixed

> No data in alertEngineSpout - handle exception
> --
>
> Key: EAGLE-1014
> URL: https://issues.apache.org/jira/browse/EAGLE-1014
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> Found the following exception log
> {code}
> 2017-04-27 03:26:40 Thread-11-alertEngineSpout-EventThread 
> org.apache.eagle.alert.engine.spout.CorrelationSpout [ERROR] error applying 
> new SpoutSpec
> java.lang.RuntimeException: java.lang.RuntimeException: No leader found for 
> partition 3
> at 
> storm.kafka.DynamicBrokersReader.getBrokerInfo(DynamicBrokersReader.java:92) 
> ~[stormjar.jar:na]
> at storm.kafka.trident.ZkBrokerReader.(ZkBrokerReader.java:42) 
> ~[stormjar.jar:na]
> at storm.kafka.KafkaUtils.makeBrokerReader(KafkaUtils.java:57) 
> ~[stormjar.jar:na]
> at storm.kafka.KafkaSpoutWrapper.open(KafkaSpoutWrapper.java:79) 
> ~[stormjar.jar:na]
> at 
> org.apache.eagle.alert.engine.spout.CorrelationSpout.createKafkaSpout(CorrelationSpout.java:355)
>  ~[stormjar.jar:na]
> at 
> org.apache.eagle.alert.engine.spout.CorrelationSpout.onReload(CorrelationSpout.java:259)
>  ~[stormjar.jar:na]
> at 
> org.apache.eagle.alert.engine.spout.CorrelationSpout.onSpoutSpecChange(CorrelationSpout.java:162)
>  ~[stormjar.jar:na]
> at 
> org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.lambda$notifySpout$0(AbstractMetadataChangeNotifyService.java:91)
>  [stormjar.jar:na]
> at java.util.ArrayList.forEach(ArrayList.java:1249) ~[na:1.8.0_91]
> at 
> org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.notifySpout(AbstractMetadataChangeNotifyService.java:91)
>  [stormjar.jar:na]
> at 
> org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.onNewConfig(ZKMetadataChangeNotifyService.java:148)
>  ~[stormjar.jar:na]
> at 
> org.apache.eagle.alert.config.ConfigBusConsumer.lambda$new$0(ConfigBusConsumer.java:44)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:293)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:287)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92)
>  ~[stormjar.jar:na]
> at 
> com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253)
>  ~[guava-11.0.2.jar:na]
> at 
> org.apache.curator.framework.listen.ListenerContainer.forEach(ListenerContainer.java:83)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.recipes.cache.NodeCache.setNewData(NodeCache.java:284)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.recipes.cache.NodeCache.processBackgroundResult(NodeCache.java:252)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.recipes.cache.NodeCache.access$300(NodeCache.java:53)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.recipes.cache.NodeCache$3.processResult(NodeCache.java:111)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl.sendToBackgroundCallback(CuratorFrameworkImpl.java:730)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:516)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.imps.GetDataBuilderImpl$3.processResult(GetDataBuilderImpl.java:254)
>  ~[stormjar.jar:na]
> at 
> org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:561) 
> ~[zookeeper-3.4.6.2.2.0.0-2041.jar:3.4.6-2041--1]
> at 
> org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498) 
> ~[zookeeper-3.4.6.2.2.0.0-2041.jar:3.4.6-2041--1]
> Caused by: java.lang.RuntimeException: No leader found for partition 3
> at 
> storm.kafka.DynamicBrokersReader.getLeaderFor(DynamicBrokersReader.java:131) 
> ~[stormjar.jar:na]
> at 
> storm.kafka.DynamicBrokersReader.getBrokerInfo(DynamicBrokersReader.java:79) 
> ~[stormjar.jar:na]
> ... 25 common frames omitted
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-1015) Add an interface to add storm configuration in an application

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-1015.
---
Resolution: Fixed

> Add an interface to add storm configuration in an application
> -
>
> Key: EAGLE-1015
> URL: https://issues.apache.org/jira/browse/EAGLE-1015
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> Apart from the application related configurations, Eagle should give an 
> interface to add some storm-related configurations, such as `workers`, 
> `topology.worker.childopts`, `topology.message.timeout.secs`, etc. 
> Here is my idea, for those configurations which start with 
> 'application.storm', Eagle will treat these configurations as storm 
> configurations. for example, 'storm.override.workers', then the value of 
> 'workers' are overridden.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-966) error: failed to run exclusive executor

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-966:
-
Fix Version/s: (was: v0.5.0)
   v0.6.0

> error: failed to run exclusive executor
> ---
>
> Key: EAGLE-966
> URL: https://issues.apache.org/jira/browse/EAGLE-966
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Jayesh
>Priority: Minor
> Fix For: v0.6.0
>
>
> following stacktrace is seen while starting the eagle service, 
> I think it happens due to no storm topology ( application) running but it may 
> have some policies defined.
> this is not affecting any functionality in eagle once you start any app 
> topology.
> {code}
> WARN  [2017-03-19 17:34:29,587] 
> org.apache.eagle.alert.coordinator.ExclusiveExecutor: failed to run exclusive 
> executor
> ! java.lang.UnsupportedOperationException: not supported yet!
> ! at 
> org.apache.eagle.alert.coordinator.TopologyMgmtService.creatTopology(TopologyMgmtService.java:72)
>  ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.alert.coordinator.impl.strategies.SameTopologySlotStrategy.reserveWorkSlots(SameTopologySlotStrategy.java:101)
>  ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.alert.coordinator.impl.WorkQueueBuilder.createQueue(WorkQueueBuilder.java:54)
>  ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.alert.coordinator.impl.GreedyPolicyScheduler.findWorkSlotQueue(GreedyPolicyScheduler.java:274)
>  ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.alert.coordinator.impl.GreedyPolicyScheduler.schedulePolicy(GreedyPolicyScheduler.java:234)
>  ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.alert.coordinator.impl.GreedyPolicyScheduler.schedule(GreedyPolicyScheduler.java:106)
>  ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.alert.coordinator.trigger.CoordinatorTrigger.lambda$run$0(CoordinatorTrigger.java:64)
>  ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.eagle.alert.coordinator.ExclusiveExecutor$1.takeLeadership(ExclusiveExecutor.java:79)
>  ~[eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.curator.framework.recipes.leader.LeaderSelector$WrappedListener.takeLeadership(LeaderSelector.java:536)
>  [eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.curator.framework.recipes.leader.LeaderSelector.doWork(LeaderSelector.java:398)
>  [eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.curator.framework.recipes.leader.LeaderSelector.doWorkLoop(LeaderSelector.java:443)
>  [eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.curator.framework.recipes.leader.LeaderSelector.access$100(LeaderSelector.java:63)
>  [eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.curator.framework.recipes.leader.LeaderSelector$2.call(LeaderSelector.java:244)
>  [eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at 
> org.apache.curator.framework.recipes.leader.LeaderSelector$2.call(LeaderSelector.java:238)
>  [eagle-topology-0.5.0-SNAPSHOT-assembly.jar:na]
> ! at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_102]
> ! at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_102]
> ! at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_102]
> ! at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_102]
> ! at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_102]
> ! at java.lang.Thread.run(Thread.java:745) [na:1.8.0_102]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (EAGLE-1018) guice with asm compatibility issue while moving to storm 1.x

[Jayesh (JIRA)]

Jayesh created EAGLE-1018:
-

 Summary: guice with asm compatibility issue while moving to storm 
1.x
 Key: EAGLE-1018
 URL: https://issues.apache.org/jira/browse/EAGLE-1018
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.6.0
Reporter: Jayesh
 Fix For: v0.6.0


{code}
WARN  [2017-05-03 19:37:17,884] 
org.apache.eagle.app.module.ApplicationExtensionLoader: Loading application 
extension modules
ERROR [2017-05-03 19:37:17,957] 
org.apache.eagle.metadata.persistence.MetadataStore: Failed to instantiate 
org.apache.eagle.metadata.store.jdbc.JDBCMetadataStore
! java.lang.ClassNotFoundException: 
org.apache.eagle.metadata.store.jdbc.JDBCMetadataStore
! at java.net.URLClassLoader.findClass(URLClassLoader.java:381) ~[na:1.8.0_102]
! at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[na:1.8.0_102]
! at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) 
~[na:1.8.0_102]
! at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[na:1.8.0_102]
! at java.lang.Class.forName0(Native Method) ~[na:1.8.0_102]
! at java.lang.Class.forName(Class.java:264) ~[na:1.8.0_102]
! at 
org.apache.eagle.metadata.persistence.MetadataStoreModuleFactory.getModule(MetadataStoreModuleFactory.java:43)
 ~[classes/:na]
! at 
org.apache.eagle.server.module.ServerModule.configure(ServerModule.java:36) 
[classes/:na]
! at com.google.inject.AbstractModule.configure(AbstractModule.java:59) 
[guice-3.0.jar:na]
! at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223) 
[guice-3.0.jar:na]
! at com.google.inject.spi.Elements.getElements(Elements.java:101) 
[guice-3.0.jar:na]
! at 
com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:133) 
[guice-3.0.jar:na]
! at 
com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103)
 [guice-3.0.jar:na]
! at com.google.inject.Guice.createInjector(Guice.java:95) [guice-3.0.jar:na]
! at com.google.inject.Guice.createInjector(Guice.java:72) [guice-3.0.jar:na]
! at com.google.inject.Guice.createInjector(Guice.java:62) [guice-3.0.jar:na]
! at 
org.apache.eagle.app.module.ApplicationExtensionLoader.load(ApplicationExtensionLoader.java:33)
 [classes/:na]
! at 
org.apache.eagle.server.module.GuiceBundleLoader.load(GuiceBundleLoader.java:52)
 [classes/:na]
! at 
org.apache.eagle.server.module.GuiceBundleLoader.load(GuiceBundleLoader.java:82)
 [classes/:na]
! at 
org.apache.eagle.server.ServerApplication.initialize(ServerApplication.java:69) 
[classes/:na]
! at io.dropwizard.Application.run(Application.java:70) 
[dropwizard-core-0.7.1.jar:0.7.1]
! at org.apache.eagle.server.ServerMain.main(ServerMain.java:44) [classes/:na]
Disconnected from the target VM, address: '127.0.0.1:60859', transport: 'socket'
Exception in thread "main" 
com.google.inject.internal.util.$ComputationException: 
java.lang.ArrayIndexOutOfBoundsException: 22333
at 
com.google.inject.internal.util.$MapMaker$StrategyImpl.compute(MapMaker.java:553)
at 
com.google.inject.internal.util.$MapMaker$StrategyImpl.compute(MapMaker.java:419)
at 
com.google.inject.internal.util.$CustomConcurrentHashMap$ComputingImpl.get(CustomConcurrentHashMap.java:2041)
at 
com.google.inject.internal.util.$StackTraceElements.forMember(StackTraceElements.java:53)
at 
com.google.inject.internal.Errors.formatInjectionPoint(Errors.java:716)
at com.google.inject.internal.Errors.formatSource(Errors.java:678)
at com.google.inject.internal.Errors.format(Errors.java:555)
at 
com.google.inject.CreationException.getMessage(CreationException.java:48)
at org.apache.eagle.server.ServerMain.main(ServerMain.java:46)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 22333
at com.google.inject.internal.asm.$ClassReader.(Unknown Source)
at com.google.inject.internal.asm.$ClassReader.(Unknown Source)
at com.google.inject.internal.asm.$ClassReader.(Unknown Source)
at 
com.google.inject.internal.util.$LineNumbers.(LineNumbers.java:62)
at 
com.google.inject.internal.util.$StackTraceElements$1.apply(StackTraceElements.java:36)
at 
com.google.inject.internal.util.$StackTraceElements$1.apply(StackTraceElements.java:33)
at 
com.google.inject.internal.util.$MapMaker$StrategyImpl.compute(MapMaker.java:549)
... 8 more

{code}

ref: https://github.com/google/guice/issues/757



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-1014) No data in alertEngineSpout - handle exception

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-1014:
--
Summary: No data in alertEngineSpout - handle exception  (was: No data in 
alertEngineSpout )

> No data in alertEngineSpout - handle exception
> --
>
> Key: EAGLE-1014
> URL: https://issues.apache.org/jira/browse/EAGLE-1014
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> Found the following exception log
> {code}
> 2017-04-27 03:26:40 Thread-11-alertEngineSpout-EventThread 
> org.apache.eagle.alert.engine.spout.CorrelationSpout [ERROR] error applying 
> new SpoutSpec
> java.lang.RuntimeException: java.lang.RuntimeException: No leader found for 
> partition 3
> at 
> storm.kafka.DynamicBrokersReader.getBrokerInfo(DynamicBrokersReader.java:92) 
> ~[stormjar.jar:na]
> at storm.kafka.trident.ZkBrokerReader.(ZkBrokerReader.java:42) 
> ~[stormjar.jar:na]
> at storm.kafka.KafkaUtils.makeBrokerReader(KafkaUtils.java:57) 
> ~[stormjar.jar:na]
> at storm.kafka.KafkaSpoutWrapper.open(KafkaSpoutWrapper.java:79) 
> ~[stormjar.jar:na]
> at 
> org.apache.eagle.alert.engine.spout.CorrelationSpout.createKafkaSpout(CorrelationSpout.java:355)
>  ~[stormjar.jar:na]
> at 
> org.apache.eagle.alert.engine.spout.CorrelationSpout.onReload(CorrelationSpout.java:259)
>  ~[stormjar.jar:na]
> at 
> org.apache.eagle.alert.engine.spout.CorrelationSpout.onSpoutSpecChange(CorrelationSpout.java:162)
>  ~[stormjar.jar:na]
> at 
> org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.lambda$notifySpout$0(AbstractMetadataChangeNotifyService.java:91)
>  [stormjar.jar:na]
> at java.util.ArrayList.forEach(ArrayList.java:1249) ~[na:1.8.0_91]
> at 
> org.apache.eagle.alert.engine.coordinator.impl.AbstractMetadataChangeNotifyService.notifySpout(AbstractMetadataChangeNotifyService.java:91)
>  [stormjar.jar:na]
> at 
> org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.onNewConfig(ZKMetadataChangeNotifyService.java:148)
>  ~[stormjar.jar:na]
> at 
> org.apache.eagle.alert.config.ConfigBusConsumer.lambda$new$0(ConfigBusConsumer.java:44)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:293)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:287)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92)
>  ~[stormjar.jar:na]
> at 
> com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253)
>  ~[guava-11.0.2.jar:na]
> at 
> org.apache.curator.framework.listen.ListenerContainer.forEach(ListenerContainer.java:83)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.recipes.cache.NodeCache.setNewData(NodeCache.java:284)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.recipes.cache.NodeCache.processBackgroundResult(NodeCache.java:252)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.recipes.cache.NodeCache.access$300(NodeCache.java:53)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.recipes.cache.NodeCache$3.processResult(NodeCache.java:111)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl.sendToBackgroundCallback(CuratorFrameworkImpl.java:730)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:516)
>  ~[stormjar.jar:na]
> at 
> org.apache.curator.framework.imps.GetDataBuilderImpl$3.processResult(GetDataBuilderImpl.java:254)
>  ~[stormjar.jar:na]
> at 
> org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:561) 
> ~[zookeeper-3.4.6.2.2.0.0-2041.jar:3.4.6-2041--1]
> at 
> org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498) 
> ~[zookeeper-3.4.6.2.2.0.0-2041.jar:3.4.6-2041--1]
> Caused by: java.lang.RuntimeException: No leader found for partition 3
> at 
> storm.kafka.DynamicBrokersReader.getLeaderFor(DynamicBrokersReader.java:131) 
> ~[stormjar.jar:na]
> at 
> storm.kafka.DynamicBrokersReader.getBrokerInfo(DynamicBrokersReader.java:79) 
> ~[stormjar.jar:na]
> ... 25 common frames omitted
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-985) Upgrade hbase dependency to 1.2.5

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-985:
-
Fix Version/s: v0.6.0

> Upgrade hbase dependency to 1.2.5
> -
>
> Key: EAGLE-985
> URL: https://issues.apache.org/jira/browse/EAGLE-985
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Fix For: v0.6.0
>
> Attachments: Screen Shot 2017-04-04 at 11.24.38 AM.png
>
>
> hbase 0.98.4 release is very old.
> There wouldn't be any new 0.98 release.
> We should upgrade to 1.2.5 which is the latest stable release.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (EAGLE-985) Upgrade hbase dependency to 1.2.5

[Jayesh (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15981841#comment-15981841
 ] 

Jayesh commented on EAGLE-985:
--

[~yuzhih...@gmail.com] lets target this for 0.6, since looks like we wont have 
time to test this with coprocessor enabled. 
with 0.6 target we will have sometime to test this.

> Upgrade hbase dependency to 1.2.5
> -
>
> Key: EAGLE-985
> URL: https://issues.apache.org/jira/browse/EAGLE-985
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Fix For: v0.6.0
>
> Attachments: Screen Shot 2017-04-04 at 11.24.38 AM.png
>
>
> hbase 0.98.4 release is very old.
> There wouldn't be any new 0.98 release.
> We should upgrade to 1.2.5 which is the latest stable release.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (EAGLE-247) Refactor Eagle Docker Image without depending on Ambari

[Jayesh (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978243#comment-15978243
 ] 

Jayesh edited comment on EAGLE-247 at 4/21/17 7:46 AM:
---

while working on docker image for 0.5 , i realize the same where ambari 
introduce not only limitations but instability into the docker container so i 
created EAGLE-997, which i think points towards the same solution. 

[~haoch] are you planning to pick this up? I can close the other one as 
duplicate then.


was (Author: jhsenjaliya):
while working on docker image for 0.5 , i realize the same where ambari 
introduce not only limitations but instability into the docker container so i 
created EAGLE-997, which i think points towards the same solution. 

[~haoch] are you planning to pick this up?

> Refactor Eagle Docker Image without depending on Ambari 
> 
>
> Key: EAGLE-247
> URL: https://issues.apache.org/jira/browse/EAGLE-247
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>
> Current version of Eagle docker is based on Ambari, which is really unstable. 
> From the scripts like 
> https://github.com/apache/incubator-eagle/tree/master/eagle-devsupport, we 
> could learn that we could definitely set up eagle without depending on Ambari 
> at all, and it will be much more clear and light-weight for end-user.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (EAGLE-942) Fetch running apps info with Yarn client

[Jayesh (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976216#comment-15976216
 ] 

Jayesh commented on EAGLE-942:
--

[~cltlfcjin], Yes i think it will be good improvement to add in eagle.
it should also remove lot of those classes that comes from yarn client.
Also YARN patch is very nice to have but will be only available after hadoop 
2.7.3. 
Thanks


> Fetch running apps info with Yarn client
> 
>
> Key: EAGLE-942
> URL: https://issues.apache.org/jira/browse/EAGLE-942
> Project: Eagle
>  Issue Type: Improvement
>  Components: App::Job Performance Monitor
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Lantao Jin
> Fix For: v0.5.0
>
>
> Since Hadoop upgrades to 2.7, /apps API returns much more data than before, 
> which burdens of the resource manager heavily. 
> The requirements:
> * support multiple Hadoop version, at least 2.4 & 2.7
> * avoid the heavy burden on resource manager for per request



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (EAGLE-1012) Some language level problems

[Jayesh (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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] [Updated] (EAGLE-998) Add eagle csd

[Jayesh (JIRA)]

 [ 
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] [Updated] (EAGLE-992) HBase Naming that unify `Hbase` and `HBase` into `HBase`

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-992:
-
Fix Version/s: (was: Future)
   v0.5.0

> 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
>  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-972) Eagle 0.5 release tasks checklist

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-972:
-
Summary: Eagle 0.5 release tasks checklist  (was: Eagle 0.5 Release Tasks)

> Eagle 0.5 release tasks checklist
> -
>
> Key: EAGLE-972
> URL: https://issues.apache.org/jira/browse/EAGLE-972
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.5.0
>Reporter: Jayesh
>  Labels: release
> Fix For: v0.5.0
>
>
> This ticket should include all the required tasks that needs to be complete 
> in order to release 0.5



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-972) Eagle 0.5 Release Tasks

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-972:
-
Summary: Eagle 0.5 Release Tasks  (was: Create 0.5 Release)

> Eagle 0.5 Release Tasks
> ---
>
> Key: EAGLE-972
> URL: https://issues.apache.org/jira/browse/EAGLE-972
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.5.0
>Reporter: Jayesh
>  Labels: release
> Fix For: v0.5.0
>
>
> This ticket should include all the required tasks that needs to be complete 
> in order to release 0.5



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-1004) Test branch-0.5 with apps on Dev/Staging environment

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-1004:
--
Summary: Test branch-0.5 with apps on Dev/Staging environment  (was: Test 
Eagle 0.5 on Dev/Staging environment)

> Test branch-0.5 with apps on Dev/Staging environment
> 
>
> Key: EAGLE-1004
> URL: https://issues.apache.org/jira/browse/EAGLE-1004
> Project: Eagle
>  Issue Type: Sub-task
>Reporter: Jayesh
> Fix For: v0.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (EAGLE-1005) cut branch 0.5

[Jayesh (JIRA)]

Jayesh created EAGLE-1005:
-

 Summary: cut branch 0.5
 Key: EAGLE-1005
 URL: https://issues.apache.org/jira/browse/EAGLE-1005
 Project: Eagle
  Issue Type: Sub-task
Reporter: Jayesh
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-1005) cut branch 0.5

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-1005.
---
Resolution: Fixed

branch-0.5 is created

> cut branch 0.5
> --
>
> Key: EAGLE-1005
> URL: https://issues.apache.org/jira/browse/EAGLE-1005
> Project: Eagle
>  Issue Type: Sub-task
>Reporter: Jayesh
>Priority: Minor
> Fix For: v0.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (EAGLE-1005) cut branch 0.5

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh reassigned EAGLE-1005:
-

Assignee: Jayesh

> cut branch 0.5
> --
>
> Key: EAGLE-1005
> URL: https://issues.apache.org/jira/browse/EAGLE-1005
> Project: Eagle
>  Issue Type: Sub-task
>Reporter: Jayesh
>Assignee: Jayesh
>Priority: Minor
> Fix For: v0.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (EAGLE-942) Fetch running apps info with Yarn client

[Jayesh (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970831#comment-15970831
 ] 

Jayesh commented on EAGLE-942:
--

[~cltlfcjin], are you targeting this change for 0.5 ? do you think you will 
have this PR sometime this month?
I think this would be very nice to have, to keep Apache Eagle efficient.

Also it would be nice if you can remove those classes that was duplicated due 
to lack of yarn client. Thanks !

> Fetch running apps info with Yarn client
> 
>
> Key: EAGLE-942
> URL: https://issues.apache.org/jira/browse/EAGLE-942
> Project: Eagle
>  Issue Type: Improvement
>  Components: App::Job Performance Monitor
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Lantao Jin
> Fix For: v0.5.0
>
>
> Since Hadoop upgrades to 2.7, /apps API returns much more data than before, 
> which burdens of the resource manager heavily. 
> The requirements:
> * support multiple Hadoop version, at least 2.4 & 2.7
> * avoid the heavy burden on resource manager for per request



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (EAGLE-984) Potential null dereference in SimpleWindowCounter#poll()

[Jayesh (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970828#comment-15970828
 ] 

Jayesh commented on EAGLE-984:
--

[~ted_yu] would you be interested in providing fix for this ?

> Potential null dereference in SimpleWindowCounter#poll()
> 
>
> Key: EAGLE-984
> URL: https://issues.apache.org/jira/browse/EAGLE-984
> Project: Eagle
>  Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
> Fix For: v0.5.0
>
>
> Here is related code:
> {code}
> public Tuple2 poll() {
> long oldestTimestamp = timeQueue.poll();
> Tuple2 pair = new Tuple2<>(oldestTimestamp, 
> counter.get(oldestTimestamp));
> {code}
> We should check the return value from timeQueue.poll() before casting to long.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-984) Potential null dereference in SimpleWindowCounter#poll()

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-984:
-
Fix Version/s: v0.5.0

> Potential null dereference in SimpleWindowCounter#poll()
> 
>
> Key: EAGLE-984
> URL: https://issues.apache.org/jira/browse/EAGLE-984
> Project: Eagle
>  Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
> Fix For: v0.5.0
>
>
> Here is related code:
> {code}
> public Tuple2 poll() {
> long oldestTimestamp = timeQueue.poll();
> Tuple2 pair = new Tuple2<>(oldestTimestamp, 
> counter.get(oldestTimestamp));
> {code}
> We should check the return value from timeQueue.poll() before casting to long.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (EAGLE-958) ElasticSearch Alert Publisher

[Jayesh (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970824#comment-15970824
 ] 

Jayesh commented on EAGLE-958:
--

[~haoch] are you planning to put this feature in 0.5 ?, can u please set v0.6.0 
if not.

I also have suggestion to convert this into generic feature to use ELK as cold 
storage ( since we will have that requirement on myside in near future), I have 
created this EP, Please let me know your thoughts: 
https://cwiki.apache.org/confluence/display/EAG/EP-19+Optional+Elastic+Search+integration+for+longer+retention



> ElasticSearch Alert Publisher
> -
>
> Key: EAGLE-958
> URL: https://issues.apache.org/jira/browse/EAGLE-958
> Project: Eagle
>  Issue Type: New Feature
>  Components: Core::Alert Engine
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> ElasticSearch Alert Publisher



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-969) duplicate email module

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-969:
-
Fix Version/s: (was: v0.5.0)
   v0.6.0

> duplicate email module
> --
>
> Key: EAGLE-969
> URL: https://issues.apache.org/jira/browse/EAGLE-969
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Jayesh
>Assignee: Jayesh
> Fix For: v0.6.0
>
>
> I see duplicate email module {{org.apache.eagle.common.mail}} and 
> {{org.apache.eagle.alert.engine.publisher.email}} both has similar email 
> functionality related classes, not sure what is the reason, but it should be 
> merged, because it can create confusion letter. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (EAGLE-988) Can't sort by Duration in Job Details Page

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh resolved EAGLE-988.
--
Resolution: Fixed

> Can't sort by Duration in Job Details Page
> --
>
> Key: EAGLE-988
> URL: https://issues.apache.org/jira/browse/EAGLE-988
> Project: Eagle
>  Issue Type: Bug
>  Components: App::Job Performance Monitor
>Affects Versions: v0.5.0
>Reporter: Chang chen
>Assignee: Jilin, Jiang
> Fix For: v0.5.0
>
> Attachments: 7864577558@chatroom_1491013604898_31.png
>
>
> Steps to reproduce
> # enter job detail list page 
> # click head of duration column



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (EAGLE-1004) Test Eagle 0.5 on Dev/Staging environment

[Jayesh (JIRA)]

Jayesh created EAGLE-1004:
-

 Summary: Test Eagle 0.5 on Dev/Staging environment
 Key: EAGLE-1004
 URL: https://issues.apache.org/jira/browse/EAGLE-1004
 Project: Eagle
  Issue Type: Sub-task
Reporter: Jayesh






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-997) use prebuilt hadoop base image for eagle docker image

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-997:
-
Description: 
currently eagle docker image is based on ambari, which while deploying requires 
entire hadoop cluster to be built by ambari shell API as a part of building 
docker image.

if we use docker image that is not only based on prebuilt hadoop but also has 
required eagle dependencies, the only thing that needs be done is to deploy 
eagle by following the deployment steps.

this gives lot of benefits
1) deployment steps can be verified when there is a change,
2) it serves as a indirect documentation on working deployment steps
3) makes it easy to test any change on eagle code ( before CI )
4) provides effective dev environment so use does have to spend time to install 
all required components.


  was:
currently eagle docker image is based on ambari, which while deploying requires 
entire hadoop cluster to be built by ambari shell API as a part of building 
docker image.

if we use docker image that is based on prebuilt hadoop, the only thing that 
needs be done is to deploy eagle by following the deployment steps.

this gives lot of benefits
1) deployment steps can be verified when there is a change,
2) it serves as a indirect documentation on working deployment steps
3) makes it easy to test any change on eagle code ( before CI )
4) provides effective dev environment so use does have to spend time to install 
all required components.



> use prebuilt hadoop base image for eagle docker image
> -
>
> Key: EAGLE-997
> URL: https://issues.apache.org/jira/browse/EAGLE-997
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Jayesh
>Assignee: Jayesh
> Fix For: v0.6.0
>
>
> currently eagle docker image is based on ambari, which while deploying 
> requires entire hadoop cluster to be built by ambari shell API as a part of 
> building docker image.
> if we use docker image that is not only based on prebuilt hadoop but also has 
> required eagle dependencies, the only thing that needs be done is to deploy 
> eagle by following the deployment steps.
> this gives lot of benefits
> 1) deployment steps can be verified when there is a change,
> 2) it serves as a indirect documentation on working deployment steps
> 3) makes it easy to test any change on eagle code ( before CI )
> 4) provides effective dev environment so use does have to spend time to 
> install all required components.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (EAGLE-997) use prebuilt hadoop base image for eagle docker image

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh updated EAGLE-997:
-
Summary: use prebuilt hadoop base image for eagle docker image  (was: move 
eagle docker image base to hadoop base image)

> use prebuilt hadoop base image for eagle docker image
> -
>
> Key: EAGLE-997
> URL: https://issues.apache.org/jira/browse/EAGLE-997
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Jayesh
>Assignee: Jayesh
> Fix For: v0.6.0
>
>
> currently eagle docker image is based on ambari, which while deploying 
> requires entire hadoop cluster to be built by ambari shell API as a part of 
> building docker image.
> if we use docker image that is based on prebuilt hadoop, the only thing that 
> needs be done is to deploy eagle by following the deployment steps.
> this gives lot of benefits
> 1) deployment steps can be verified when there is a change,
> 2) it serves as a indirect documentation on working deployment steps
> 3) makes it easy to test any change on eagle code ( before CI )
> 4) provides effective dev environment so use does have to spend time to 
> install all required components.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (EAGLE-997) move eagle docker image base to hadoop base image

[Jayesh (JIRA)]

Jayesh created EAGLE-997:


 Summary: move eagle docker image base to hadoop base image
 Key: EAGLE-997
 URL: https://issues.apache.org/jira/browse/EAGLE-997
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Jayesh
Assignee: Jayesh
 Fix For: v0.6.0


currently eagle docker image is based on ambari, which while deploying requires 
entire hadoop cluster to be built by ambari shell API as a part of building 
docker image.

if we use docker image that is based on prebuilt hadoop, the only thing that 
needs be done is to deploy eagle by following the deployment steps.

this gives lot of benefits
1) deployment steps can be verified when there is a change,
2) it serves as a indirect documentation on working deployment steps
3) makes it easy to test any change on eagle code ( before CI )
4) provides effective dev environment so use does have to spend time to install 
all required components.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (EAGLE-973) update site document content

[Jayesh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayesh reassigned EAGLE-973:


Assignee: Hao Chen

> update site document content
> 
>
> Key: EAGLE-973
> URL: https://issues.apache.org/jira/browse/EAGLE-973
> Project: Eagle
>  Issue Type: Sub-task
>Reporter: Jayesh
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)