[jira] [Created] (EAGLE-1090) make merge-pr script python 3 compatible
Jayesh created EAGLE-1090: - Summary: make merge-pr script python 3 compatible Key: EAGLE-1090 URL: https://issues.apache.org/jira/browse/EAGLE-1090 Project: Eagle Issue Type: Improvement Reporter: Jayesh Assignee: Jayesh * use requests instead of urllib * update print statements -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (EAGLE-1085) alertService throws missing field exception when JDBC is deep storage
[
https://issues.apache.org/jira/browse/EAGLE-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayesh updated EAGLE-1085:
--
Affects Version/s: v0.5.1
v0.5.0
Fix Version/s: v0.5.1
Component/s: Core::Query Engine
> alertService throws missing field exception when JDBC is deep storage
> -
>
> Key: EAGLE-1085
> URL: https://issues.apache.org/jira/browse/EAGLE-1085
> Project: Eagle
> Issue Type: Bug
> Components: Core::Query Engine
>Affects Versions: v0.5.0, v0.5.1
>Reporter: Jayesh
>Priority: Major
> Fix For: v0.5.1
>
>
> request query: AlertService[@siteId="test_site"]<@severity>\{count}
> Exception: java.io.IOException: org.apache.torque.TorqueException:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column
> 'alert_detail_alert_detail.count' in 'field list'
>
> looks like JDBC mapping of the query aggregation is not doing it right.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (EAGLE-1085) alertService throws missing field exception when JDBC is deep storage
Jayesh created EAGLE-1085:
-
Summary: alertService throws missing field exception when JDBC is
deep storage
Key: EAGLE-1085
URL: https://issues.apache.org/jira/browse/EAGLE-1085
Project: Eagle
Issue Type: Bug
Reporter: Jayesh
request query: AlertService[@siteId="test_site"]<@severity>\{count}
Exception: java.io.IOException: org.apache.torque.TorqueException:
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column
'alert_detail_alert_detail.count' in 'field list'
looks like JDBC mapping of the query aggregation is not doing it right.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (EAGLE-1082) The server script can't be started from the same directory
[ https://issues.apache.org/jira/browse/EAGLE-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh resolved EAGLE-1082. --- Resolution: Fixed > The server script can't be started from the same directory > -- > > Key: EAGLE-1082 > URL: https://issues.apache.org/jira/browse/EAGLE-1082 > Project: Eagle > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > As reported here on the mailing list, it's not possible to run > "./eagle-server.sh start". Instead it must be run from the "bin" directory: > > http://mail-archives.apache.org/mod_mbox/eagle-dev/201802.mbox/%3CCAB8XdGAAb1EvRjc09uNjbBYJ-SXaDo10eqXgLpYaucx_u6nf_A%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (EAGLE-1080) Fix checkstyle errors in the eagle-query-base module
[ https://issues.apache.org/jira/browse/EAGLE-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh resolved EAGLE-1080. --- Resolution: Fixed > Fix checkstyle errors in the eagle-query-base module > > > Key: EAGLE-1080 > URL: https://issues.apache.org/jira/browse/EAGLE-1080 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: v0.5.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (EAGLE-1083) Upgrade Storm to 0.9.7
[ https://issues.apache.org/jira/browse/EAGLE-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh resolved EAGLE-1083. --- Resolution: Fixed > Upgrade Storm to 0.9.7 > -- > > Key: EAGLE-1083 > URL: https://issues.apache.org/jira/browse/EAGLE-1083 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > We should update Storm to the latest minor release of 0.9.x (0.9.7). In > addition, we are using two different versions of Kafka which should be > aligned. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (EAGLE-968) using Email Notification Feature throws IncompatibleClassChangeError
[
https://issues.apache.org/jira/browse/EAGLE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayesh resolved EAGLE-968.
--
Resolution: Fixed
> 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
>Priority: Major
> Fix For: v0.5.1
>
> Attachments: 941.patch
>
>
> {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
> org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:262)
> ~[stormjar.jar:?]
[jira] [Assigned] (EAGLE-968) using Email Notification Feature throws IncompatibleClassChangeError
[
https://issues.apache.org/jira/browse/EAGLE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayesh reassigned EAGLE-968:
Assignee: (was: Jayesh)
> 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
>Priority: Major
> Fix For: v0.5.1
>
> Attachments: 941.patch
>
>
> {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
> org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:262)
>
[jira] [Resolved] (EAGLE-331) avoid to use junit.framework.Assert
[ https://issues.apache.org/jira/browse/EAGLE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh resolved EAGLE-331. -- Resolution: Fixed > avoid to use junit.framework.Assert > --- > > Key: EAGLE-331 > URL: https://issues.apache.org/jira/browse/EAGLE-331 > Project: Eagle > Issue Type: Bug >Reporter: Edward Zhang >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: v0.5.1 > > > all eagle code should not use deprecated Assert -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (EAGLE-476) Outdated HBase audit log parser
[ https://issues.apache.org/jira/browse/EAGLE-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh resolved EAGLE-476. -- Resolution: Fixed > Outdated HBase audit log parser > --- > > Key: EAGLE-476 > URL: https://issues.apache.org/jira/browse/EAGLE-476 > Project: Eagle > Issue Type: Bug >Reporter: Peter Kim >Priority: Major > Fix For: v0.5.0 > > > The parsing logic for HBase audit logs (security logs) fails for some of the > newly formatted hbase audit logs. Obviously, this can cause the eagle service > to overlook these log lines, and fail to generate alerts, which can have a > severe outcome in terms of security. For example: > 2016-08-17 14:09:52,232 TRACE > SecurityLogger.org.apache.hadoop.hbase.security.access.AccessController: > Access allowed for user petkim; reason: Table permission granted; remote > address: /127.0.0.1; request: flush; context: (user=petkim, scope=hbase:meta, > params=[table=hbase:meta],action=ADMIN) > 2016-08-17 14:04:27,042 TRACE > SecurityLogger.org.apache.hadoop.hbase.security.access.AccessController: > Access allowed for user petkim; reason: All users allowed; remote address: > /111.1.1.1; request: scan; context: (user=petkim, scope=hbase:meta, > family=info, params=[table=hbase:meta,family=info],action=READ) > These log lines are not parsed correctly as the fields that the current regex > matches are static. The first log does not have the field "family" and the > second one has a new field named "params". So, the parsing logic fails here. > To fix this and ensure scalability (reliable no matter how many fields are > omitted or added), I will extend the current parsing logic to more reliable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (EAGLE-476) Outdated HBase audit log parser
[ https://issues.apache.org/jira/browse/EAGLE-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh reassigned EAGLE-476: Assignee: Peter Kim > Outdated HBase audit log parser > --- > > Key: EAGLE-476 > URL: https://issues.apache.org/jira/browse/EAGLE-476 > Project: Eagle > Issue Type: Bug >Reporter: Peter Kim >Assignee: Peter Kim >Priority: Major > Fix For: v0.5.0 > > > The parsing logic for HBase audit logs (security logs) fails for some of the > newly formatted hbase audit logs. Obviously, this can cause the eagle service > to overlook these log lines, and fail to generate alerts, which can have a > severe outcome in terms of security. For example: > 2016-08-17 14:09:52,232 TRACE > SecurityLogger.org.apache.hadoop.hbase.security.access.AccessController: > Access allowed for user petkim; reason: Table permission granted; remote > address: /127.0.0.1; request: flush; context: (user=petkim, scope=hbase:meta, > params=[table=hbase:meta],action=ADMIN) > 2016-08-17 14:04:27,042 TRACE > SecurityLogger.org.apache.hadoop.hbase.security.access.AccessController: > Access allowed for user petkim; reason: All users allowed; remote address: > /111.1.1.1; request: scan; context: (user=petkim, scope=hbase:meta, > family=info, params=[table=hbase:meta,family=info],action=READ) > These log lines are not parsed correctly as the fields that the current regex > matches are static. The first log does not have the field "family" and the > second one has a new field named "params". So, the parsing logic fails here. > To fix this and ensure scalability (reliable no matter how many fields are > omitted or added), I will extend the current parsing logic to more reliable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (EAGLE-445) convert eagle-hdfs-auditlog app to use new app framework
[ https://issues.apache.org/jira/browse/EAGLE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh resolved EAGLE-445. -- Resolution: Fixed > convert eagle-hdfs-auditlog app to use new app framework > > > Key: EAGLE-445 > URL: https://issues.apache.org/jira/browse/EAGLE-445 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Major > Fix For: v0.5.0 > > > eagle-hdfs-auditlog should use new app framework to manage its lifecycle -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (EAGLE-1075) Can't specify configuration options for AlertFilePublisher
[ https://issues.apache.org/jira/browse/EAGLE-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh reassigned EAGLE-1075: - Assignee: Jayesh > Can't specify configuration options for AlertFilePublisher > -- > > Key: EAGLE-1075 > URL: https://issues.apache.org/jira/browse/EAGLE-1075 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Jayesh >Priority: Major > Fix For: v0.5.1 > > > Right now it's not possible to specify the configuration options for the > AlertFilePublisher in the UI. So for example we can't configure the file > name/path. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (EAGLE-1075) Can't specify configuration options for AlertFilePublisher
[ https://issues.apache.org/jira/browse/EAGLE-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh reassigned EAGLE-1075: - Assignee: (was: Jayesh) > Can't specify configuration options for AlertFilePublisher > -- > > Key: EAGLE-1075 > URL: https://issues.apache.org/jira/browse/EAGLE-1075 > Project: Eagle > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Priority: Major > Fix For: v0.5.1 > > > Right now it's not possible to specify the configuration options for the > AlertFilePublisher in the UI. So for example we can't configure the file > name/path. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (EAGLE-331) avoid to use junit.framework.Assert
[ https://issues.apache.org/jira/browse/EAGLE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347349#comment-16347349 ] Jayesh commented on EAGLE-331: -- [~coheigea], can u pease assign this to yourself, Jira cant find ur username somehow. Thanks > avoid to use junit.framework.Assert > --- > > Key: EAGLE-331 > URL: https://issues.apache.org/jira/browse/EAGLE-331 > Project: Eagle > Issue Type: Bug >Reporter: Edward Zhang >Priority: Trivial > > all eagle code should not use deprecated Assert -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (EAGLE-331) avoid to use junit.framework.Assert
[ https://issues.apache.org/jira/browse/EAGLE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh reassigned EAGLE-331: Assignee: (was: Lingang Deng) > avoid to use junit.framework.Assert > --- > > Key: EAGLE-331 > URL: https://issues.apache.org/jira/browse/EAGLE-331 > Project: Eagle > Issue Type: Bug >Reporter: Edward Zhang >Priority: Trivial > > all eagle code should not use deprecated Assert -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (EAGLE-1025) bump version on master
[ https://issues.apache.org/jira/browse/EAGLE-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh resolved EAGLE-1025. --- Resolution: Fixed > bump version on master > -- > > Key: EAGLE-1025 > URL: https://issues.apache.org/jira/browse/EAGLE-1025 > Project: Eagle > Issue Type: Sub-task >Reporter: Jayesh >Assignee: Jayesh >Priority: Minor > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (EAGLE-1068) Upgrade siddhi dependency to 4.0.0-M120
[ https://issues.apache.org/jira/browse/EAGLE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh reopened EAGLE-1068: --- [~haoch], reopening the issue, please update here with PR if its not correct. Thanks > Upgrade siddhi dependency to 4.0.0-M120 > --- > > Key: EAGLE-1068 > URL: https://issues.apache.org/jira/browse/EAGLE-1068 > Project: Eagle > Issue Type: Improvement > Components: Core::Alert Engine >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen >Priority: Blocker > Fix For: v0.5.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (EAGLE-1067) Policy page should also have time range or date picker
[ https://issues.apache.org/jira/browse/EAGLE-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-1067: -- Priority: Minor (was: Major) > Policy page should also have time range or date picker > --- > > Key: EAGLE-1067 > URL: https://issues.apache.org/jira/browse/EAGLE-1067 > Project: Eagle > Issue Type: Improvement > Components: Core::UI Engine >Affects Versions: v0.5.0 >Reporter: Jayesh >Priority: Minor > Attachments: Screen Shot 2017-10-12 at 3.57.59 PM.png > > > As shown in the screenshot, each policy page, which shows the alerts when it > is saved in eagle store, should have datepicker to look into old alerts for > that specific policy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (EAGLE-1067) Policy page should also have time range or date picker
Jayesh created EAGLE-1067: - Summary: Policy page should also have time range or date picker Key: EAGLE-1067 URL: https://issues.apache.org/jira/browse/EAGLE-1067 Project: Eagle Issue Type: Improvement Components: Core::UI Engine Affects Versions: v0.5.0 Reporter: Jayesh Attachments: Screen Shot 2017-10-12 at 3.57.59 PM.png As shown in the screenshot, each policy page, which shows the alerts when it is saved in eagle store, should have datepicker to look into old alerts for that specific policy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (EAGLE-1066) All TimeZone values are not considered for UI
Jayesh created EAGLE-1066: - Summary: All TimeZone values are not considered for UI Key: EAGLE-1066 URL: https://issues.apache.org/jira/browse/EAGLE-1066 Project: Eagle Issue Type: Bug Components: Core::UI Engine Affects Versions: v0.5.0 Reporter: Jayesh service.timezone value is correctly parsed in eagle backend service, but its not correctly parsed on ui side and its limited to UTC and GMT values only because of the way of calculating timezone is via UTC offset logic. so values like "America/Los_Angeles" works fine on the backend codebased but throws un-parsable error on UI because it expects only UTC and GMT values. this values are important to consider daylight saving time. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (EAGLE-1065) support new Siddhi features by upgrading siddhi version to 4.0
Jayesh created EAGLE-1065: - Summary: support new Siddhi features by upgrading siddhi version to 4.0 Key: EAGLE-1065 URL: https://issues.apache.org/jira/browse/EAGLE-1065 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Jayesh Assignee: Jayesh Fix For: v0.6.0 latest Siddhi has lot of new feature that would be very useful for eagle to define new kinds of policies, specially in the area of absence, patterns and windows. seems like there are also API changes, we may have to do lot of code change with this upgrade. Although we need to wait for its stable version release : https://github.com/wso2/siddhi , I am creating this task to take care of this important ( by feature list) and major siddhi upgrade. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (EAGLE-1064) view data source link not working on policy setting tab
Jayesh created EAGLE-1064: - Summary: view data source link not working on policy setting tab Key: EAGLE-1064 URL: https://issues.apache.org/jira/browse/EAGLE-1064 Project: Eagle Issue Type: Bug Components: Core::UI Engine Affects Versions: v0.5.0 Reporter: Jayesh Priority: Minor Attachments: Screen Shot 2017-09-20 at 2.17.12 PM.png attaching screenshot of UI error when you click on "view data source" link on policy page -> policy setting -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-985) Upgrade hbase dependency to 1.2.5
[ https://issues.apache.org/jira/browse/EAGLE-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16163332#comment-16163332 ] Jayesh commented on EAGLE-985: -- Hi Can u pls disable the periodic updates to this ticket? Thanks Jayesh > 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.4.14#64029)
[jira] [Created] (EAGLE-1062) any change to policy resets "Alert De-duplication Interval(min)" to 30
Jayesh created EAGLE-1062: - Summary: any change to policy resets "Alert De-duplication Interval(min)" to 30 Key: EAGLE-1062 URL: https://issues.apache.org/jira/browse/EAGLE-1062 Project: Eagle Issue Type: Bug Components: Core::UI Engine Affects Versions: v0.5.0 Reporter: Jayesh Priority: Minor Fix For: v0.5.1 reproducing steps 1. create policy with "Alert De-duplication Interval(min)" set to 1 2. after the policy created , edit it again and change policy definition string by typing something. 3. notice the value of "Alert De-duplication Interval(min)" will be reset to 30 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (EAGLE-1060) remove SNAPSHOT from version
[
https://issues.apache.org/jira/browse/EAGLE-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayesh resolved EAGLE-1060.
---
Resolution: Fixed
> remove SNAPSHOT from version
>
>
> Key: EAGLE-1060
> URL: https://issues.apache.org/jira/browse/EAGLE-1060
> Project: Eagle
> Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Jayesh
>Assignee: Jayesh
>Priority: Minor
> Fix For: v0.5.0
>
>
> As pointed out by Hao
> {quote}
> The downloaded source package version is 0.5.0-SNAPSHOT, I think we should
> change to 0.5.0 instead.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (EAGLE-1060) remove SNAPSHOT from version
[
https://issues.apache.org/jira/browse/EAGLE-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayesh updated EAGLE-1060:
--
Description:
As pointed out by Hao
{quote}
The downloaded source package version is 0.5.0-SNAPSHOT, I think we should
change to 0.5.0 instead.
{quote}
> remove SNAPSHOT from version
>
>
> Key: EAGLE-1060
> URL: https://issues.apache.org/jira/browse/EAGLE-1060
> Project: Eagle
> Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Jayesh
>Assignee: Jayesh
>Priority: Minor
> Fix For: v0.5.0
>
>
> As pointed out by Hao
> {quote}
> The downloaded source package version is 0.5.0-SNAPSHOT, I think we should
> change to 0.5.0 instead.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (EAGLE-1060) remove SNAPSHOT from version
Jayesh created EAGLE-1060: - Summary: remove SNAPSHOT from version Key: EAGLE-1060 URL: https://issues.apache.org/jira/browse/EAGLE-1060 Project: Eagle Issue Type: Sub-task Affects Versions: v0.5.0 Reporter: Jayesh Assignee: Jayesh Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (EAGLE-973) update site document content
[ https://issues.apache.org/jira/browse/EAGLE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108061#comment-16108061 ] Jayesh commented on EAGLE-973: -- [~haoch], can u please remove "incubating" from the latest site doc? thanks > 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.4.14#64029)
[jira] [Commented] (EAGLE-973) update site document content
[ https://issues.apache.org/jira/browse/EAGLE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16104659#comment-16104659 ] Jayesh commented on EAGLE-973: -- ya, i think just updating link should be fine, and move older doc under https://eagle.apache.org/docs/0.4/ > 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.4.14#64029)
[jira] [Commented] (EAGLE-973) update site document content
[ https://issues.apache.org/jira/browse/EAGLE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16104584#comment-16104584 ] Jayesh commented on EAGLE-973: -- Hi Hao, Can you please deploy the latest site doc under eagle's doc ? so basically https://eagle.apache.org/docs link points to the latest docs site? Thanks > 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.4.14#64029)
[jira] [Resolved] (EAGLE-1058) add missing license header
[ https://issues.apache.org/jira/browse/EAGLE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh resolved EAGLE-1058. --- Resolution: Fixed > add missing license header > -- > > Key: EAGLE-1058 > URL: https://issues.apache.org/jira/browse/EAGLE-1058 > 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.4.14#64029)
[jira] [Created] (EAGLE-1058) add missing license header
Jayesh created EAGLE-1058: - Summary: add missing license header Key: EAGLE-1058 URL: https://issues.apache.org/jira/browse/EAGLE-1058 Project: Eagle Issue Type: Sub-task Reporter: Jayesh Assignee: Jayesh Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-1025) bump version on master
[ https://issues.apache.org/jira/browse/EAGLE-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-1025: -- Fix Version/s: (was: v0.5.1) v0.5.0 > 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 > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-975) deploy site
[ https://issues.apache.org/jira/browse/EAGLE-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-975: - Fix Version/s: (was: v0.5.1) v0.5.0 > deploy site > --- > > Key: EAGLE-975 > URL: https://issues.apache.org/jira/browse/EAGLE-975 > Project: Eagle > Issue Type: Sub-task >Reporter: Jayesh >Assignee: Hao Chen > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-974) validate current open tickets
[ https://issues.apache.org/jira/browse/EAGLE-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-974: - Fix Version/s: (was: v0.5.1) v0.5.0 > validate current open tickets > - > > Key: EAGLE-974 > URL: https://issues.apache.org/jira/browse/EAGLE-974 > Project: Eagle > Issue Type: Sub-task >Reporter: Jayesh > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-973) update site document content
[ 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.1) v0.5.0 > 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.4.14#64029)
[jira] [Updated] (EAGLE-972) Eagle 0.5 release tasks checklist
[ https://issues.apache.org/jira/browse/EAGLE-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-972: - Fix Version/s: (was: v0.5.1) v0.5.0 > 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.4.14#64029)
[jira] [Updated] (EAGLE-668) Support properties type in text area instead input field of configuration
[ https://issues.apache.org/jira/browse/EAGLE-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-668: - Fix Version/s: (was: v0.5.0) v0.5.1 > Support properties type in text area instead input field of configuration > -- > > Key: EAGLE-668 > URL: https://issues.apache.org/jira/browse/EAGLE-668 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-606) Add multiple hadoop version assembly application (topology) package
[
https://issues.apache.org/jira/browse/EAGLE-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayesh updated EAGLE-606:
-
Fix Version/s: (was: v0.5.0)
v0.5.1
> Add multiple hadoop version assembly application (topology) package
> ---
>
> Key: EAGLE-606
> URL: https://issues.apache.org/jira/browse/EAGLE-606
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: wujinhu
> Fix For: v0.5.1
>
>
> Add multiple hadoop version application (topology) assembly package, for
> example:
> {code}
> lib/
> * eagle-topology-assembly-hadoop-2.6.jar
> * eagle-topology-assembly-hadoop-2.7.jar
> * eagle-topology-assembly-hadoop-X.X.jar
> {code}
> and add version-based building profile for different version:
> {code}
> mvn package -Phadoop-2.6
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (EAGLE-667) Should streat storm "KILLED" as "STOPPING" in eagle
[ https://issues.apache.org/jira/browse/EAGLE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-667: - Fix Version/s: (was: v0.5.0) v0.5.1 > Should streat storm "KILLED" as "STOPPING" in eagle > --- > > Key: EAGLE-667 > URL: https://issues.apache.org/jira/browse/EAGLE-667 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.1 > > > Should streat storm "KILLED" as "STOPPING" in eagle -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-920) mr failed job trouble shooting
[
https://issues.apache.org/jira/browse/EAGLE-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayesh updated EAGLE-920:
-
Fix Version/s: (was: v0.5.0)
v0.5.1
> mr failed job trouble shooting
> --
>
> Key: EAGLE-920
> URL: https://issues.apache.org/jira/browse/EAGLE-920
> Project: Eagle
> Issue Type: Improvement
> Components: App::Job Performance Monitor
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.1
>
>
> We will follow below steps when we find a failed mr job.
> 1. get error category distribution of the job via api
> query=TaskAttemptErrorCategoryService[@site="sandbox" and
> @jobId="job_1486726244016_162594"]<@errorCategory>{count}
> 2. get error category - error message mapping and failed task attempts list
> query=JobErrorMappingService[@site="sandbox" and
> @jobId="job_1486726244016_162594" and
> @errorCategory="java.lang.RuntimeException"]
> 3. dive into one task attempt
> query=TaskAttemptExecutionService[@site="sandbox" and
> @taskAttemptId="attempt_1486726244016_162594_m_002451_1"]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (EAGLE-410) stream tumbling window aggregate library
[ https://issues.apache.org/jira/browse/EAGLE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-410: - Fix Version/s: (was: v0.5.0) v0.5.1 > stream tumbling window aggregate library > > > Key: EAGLE-410 > URL: https://issues.apache.org/jira/browse/EAGLE-410 > Project: Eagle > Issue Type: Task >Affects Versions: v0.5.0 >Reporter: Edward Zhang >Assignee: Edward Zhang > Fix For: v0.5.1 > > > Many use cases need aggregate data in streaming process, but Storm does not > provide high level aggregation API. The most frequently used example is to > aggregate data per minute while data is streamlined. > After investigation, we found Siddhi CEP engine is good for this task. > https://docs.wso2.com/display/CEP420/Inbuilt+Windows#InbuiltWindows-externalTimeBatchexternalTimeBatch > This ticket will develop a preview of simple aggregation API for Eagle use > case. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-771) AlertEngine: Make publishment kafka endpoint as optional
[ https://issues.apache.org/jira/browse/EAGLE-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-771: - Fix Version/s: (was: v0.5.0) v0.5.1 > AlertEngine: Make publishment kafka endpoint as optional > > > Key: EAGLE-771 > URL: https://issues.apache.org/jira/browse/EAGLE-771 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Garrett Li > Fix For: v0.5.1 > > > For alert engine runtime, current kafka publishment have explicitly endpoint > set, but in real deployment, these kafka endpoint are mostly the same the > spout kafka url. > So we could make it as optional and by default reuse the kafka endpoint in > the application.conf. This help reduce the redundancy of the metadata, and > have a benefit that metadata would be the same for different deployment > environments. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-477) eagle-data-process project clean up to contain only common processing classes
[ https://issues.apache.org/jira/browse/EAGLE-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-477: - Fix Version/s: (was: v0.5.0) v0.5.1 > eagle-data-process project clean up to contain only common processing classes > - > > Key: EAGLE-477 > URL: https://issues.apache.org/jira/browse/EAGLE-477 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Minor > Fix For: v0.5.1 > > > eagle-data-process was used for orchestrating application logic, but now it > is not useful any more, we only need keep some common classes for example > spout factory and some custom partitioning code -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-984) Potential null dereference in SimpleWindowCounter#poll()
[
https://issues.apache.org/jira/browse/EAGLE-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayesh updated EAGLE-984:
-
Fix Version/s: (was: v0.5.0)
v0.5.1
> 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.1
>
>
> 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.4.14#64029)
[jira] [Updated] (EAGLE-486) upgrade storm and kafka to a version which is consistent with HDP sandbox 2.4 and CDH 5.X
[ https://issues.apache.org/jira/browse/EAGLE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-486: - Fix Version/s: (was: v0.5.0) v0.5.1 > upgrade storm and kafka to a version which is consistent with HDP sandbox 2.4 > and CDH 5.X > - > > Key: EAGLE-486 > URL: https://issues.apache.org/jira/browse/EAGLE-486 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Edward Zhang > Fix For: v0.5.1 > > > Storm and Kafka can be upgraded to get better new features and the versions > can be consistent with HDP sandbox 2.4 and CDH5.x -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-534) Integrate typesafe-config with DropWizard
[ https://issues.apache.org/jira/browse/EAGLE-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-534: - Fix Version/s: (was: v0.5.0) v0.5.1 > Integrate typesafe-config with DropWizard > - > > Key: EAGLE-534 > URL: https://issues.apache.org/jira/browse/EAGLE-534 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.4.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.1 > > > Eagle server mix YAML and typesafe-config, it's a little tricky, better > solution is to use consistent configuration library. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-444) convert eagle-gc app to use new app framework
[ https://issues.apache.org/jira/browse/EAGLE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-444: - Fix Version/s: (was: v0.5.0) v0.5.1 > convert eagle-gc app to use new app framework > - > > Key: EAGLE-444 > URL: https://issues.apache.org/jira/browse/EAGLE-444 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Edward Zhang >Assignee: Edward Zhang > Fix For: v0.5.1 > > > eagle-gc app should use new app framework to manage its lifecycle -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-799) Can not get hbase info by service api when the master becomes not available
[ https://issues.apache.org/jira/browse/EAGLE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-799: - Fix Version/s: (was: v0.5.0) v0.5.1 > Can not get hbase info by service api when the master becomes not available > --- > > Key: EAGLE-799 > URL: https://issues.apache.org/jira/browse/EAGLE-799 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: yupu >Assignee: yupu > Fix For: v0.5.1 > > > Can not get hbase info by service api when the master becomes not available -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-657) EagleServiceMetricSink
[
https://issues.apache.org/jira/browse/EAGLE-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayesh updated EAGLE-657:
-
Fix Version/s: (was: v0.5.0)
v0.5.1
> EagleServiceMetricSink
> --
>
> Key: EAGLE-657
> URL: https://issues.apache.org/jira/browse/EAGLE-657
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.1
>
>
> Persist metric to eagle metric store
> {code}
> {
> metric {
>enable: true
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (EAGLE-955) Metric Explorer and Customized Dashboard
[ https://issues.apache.org/jira/browse/EAGLE-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-955: - Fix Version/s: (was: v0.5.0) v0.5.1 > Metric Explorer and Customized Dashboard > > > Key: EAGLE-955 > URL: https://issues.apache.org/jira/browse/EAGLE-955 > Project: Eagle > Issue Type: New Feature > Components: Core::UI Engine >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen >Priority: Critical > Fix For: v0.5.1 > > > https://cwiki.apache.org/confluence/display/EAG/EP-18+Metric+Explorer+and+Customized+Dashboard#EP-18MetricExplorerandCustomizedDashboard-MetadataDesign -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-842) mr running job count in zookeeper does not match the number in hbase
[ https://issues.apache.org/jira/browse/EAGLE-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-842: - Fix Version/s: (was: v0.5.0) v0.5.1 > mr running job count in zookeeper does not match the number in hbase > > > Key: EAGLE-842 > URL: https://issues.apache.org/jira/browse/EAGLE-842 > Project: Eagle > Issue Type: Bug > Components: App::Job Performance Monitor >Affects Versions: v0.5.0 >Reporter: wujinhu >Assignee: Lingang Deng > Fix For: v0.5.1 > > > As you know, we save running job basic information in zookeeper and will be > moved when the job finished. However, as time goes on, some running job basic > information still exists in zookeeper, and when you run the zookeeper command > get /apps/mr/running/sandbox in zk shell, the number increases slowly. You > can compare this with the RUNNING number in JPM Web widget. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-541) Application policy template framework
[ https://issues.apache.org/jira/browse/EAGLE-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-541: - Fix Version/s: (was: v0.5.0) v0.5.1 > Application policy template framework > - > > Key: EAGLE-541 > URL: https://issues.apache.org/jira/browse/EAGLE-541 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.1 > > > policy is pretty complex for example it should contain > 1) siddhi expression (filter, timed window, etc.) > 2) data partition keys > 3) dedupe configuration > 4) publishment configuration > Eagle should provide a wizard for user to easily onboard polices whatever it > is a simple filtering policy or complicated timed windows -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-826) Coordinator throws NullPointerException when generateSpoutMonitorMetadata
[ https://issues.apache.org/jira/browse/EAGLE-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-826: - Fix Version/s: (was: v0.5.0) v0.5.1 > Coordinator throws NullPointerException when generateSpoutMonitorMetadata > - > > Key: EAGLE-826 > URL: https://issues.apache.org/jira/browse/EAGLE-826 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: wujinhu >Assignee: Garrett Li > Fix For: v0.5.1 > > > Coordinator throws NullPointerException when generateSpoutMonitorMetadata > because data source is empty, should catch this exception -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-792) Resolve google-fonts external connection blocking problem in AdminLTE
[ https://issues.apache.org/jira/browse/EAGLE-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-792: - Fix Version/s: (was: v0.5.0) v0.5.1 > Resolve google-fonts external connection blocking problem in AdminLTE > - > > Key: EAGLE-792 > URL: https://issues.apache.org/jira/browse/EAGLE-792 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Jilin, Jiang > Fix For: v0.5.1 > > > Resolve google-fonts connection problem in AdminLTE when having no access to > external network. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-364) Kafka Spout with kerberos
[ https://issues.apache.org/jira/browse/EAGLE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-364: - Fix Version/s: (was: v0.5.0) v0.5.1 > Kafka Spout with kerberos > - > > Key: EAGLE-364 > URL: https://issues.apache.org/jira/browse/EAGLE-364 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.3.0, v0.4.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.1 > > > Support Kafka Spout with kerberos -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-976) verify docs instructions
[ https://issues.apache.org/jira/browse/EAGLE-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-976: - Fix Version/s: (was: v0.5.0) v0.5.1 > verify docs instructions > > > Key: EAGLE-976 > URL: https://issues.apache.org/jira/browse/EAGLE-976 > 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] [Updated] (EAGLE-942) Fetch running apps info with Yarn client
[ https://issues.apache.org/jira/browse/EAGLE-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-942: - Fix Version/s: (was: v0.5.0) v0.5.1 > 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.1 > > > 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.4.14#64029)
[jira] [Updated] (EAGLE-243) Set up Eagle IT (Integration Test) Suite
[ https://issues.apache.org/jira/browse/EAGLE-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-243: - Fix Version/s: (was: v0.5.0) v0.5.1 > Set up Eagle IT (Integration Test) Suite > - > > Key: EAGLE-243 > URL: https://issues.apache.org/jira/browse/EAGLE-243 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.3.0 >Reporter: Hao Chen >Assignee: Michael Wu > Fix For: v0.5.1 > > > setup a integration test CI for eagle -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-962) The status of job list always show Running
[ https://issues.apache.org/jira/browse/EAGLE-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-962: - Fix Version/s: (was: v0.5.0) v0.5.1 > The status of job list always show Running > -- > > Key: EAGLE-962 > URL: https://issues.apache.org/jira/browse/EAGLE-962 > Project: Eagle > Issue Type: Bug > Components: App::Job Performance Monitor >Affects Versions: v0.5.0 > Environment: CDH 5.4.3 >Reporter: Chang chen >Assignee: Hao Chen > Fix For: v0.5.1 > > Attachments: eagle-jpm-bug0.PNG > > > Steps to reproduce: > # go to Job List page > # select "last 24 hours" in **time range selector** > Then you can see the status of all jobs are all RUNNING. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-921) Integrate role-based Authentication in API and UI
[ https://issues.apache.org/jira/browse/EAGLE-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-921: - Fix Version/s: (was: v0.5.0) v0.5.1 > Integrate role-based Authentication in API and UI > - > > Key: EAGLE-921 > URL: https://issues.apache.org/jira/browse/EAGLE-921 > Project: Eagle > Issue Type: New Feature > Components: Core::Eagle Server >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.1 > > > Integrate role-based Authentication in API and UI -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-677) Hadoop JMX Collector Support HA switching
[ https://issues.apache.org/jira/browse/EAGLE-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-677: - Fix Version/s: (was: v0.5.0) v0.5.1 > Hadoop JMX Collector Support HA switching > - > > Key: EAGLE-677 > URL: https://issues.apache.org/jira/browse/EAGLE-677 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-389) Integrate application streams as Alerting data source (managed kafka topic) & stream
[ https://issues.apache.org/jira/browse/EAGLE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-389: - Fix Version/s: (was: v0.5.0) v0.5.1 > Integrate application streams as Alerting data source (managed kafka topic) & > stream > > > Key: EAGLE-389 > URL: https://issues.apache.org/jira/browse/EAGLE-389 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.4.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.1 > > > * *Kafka2TupleMetadata*: any integrated streams with kafka information > * *StreamDefinition*: Integrated StreamDefinition togather with defined > StreamDefinition should be part of alerting streams. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-493) Create alert metadata based on application stream sink configuration
[ https://issues.apache.org/jira/browse/EAGLE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-493: - Fix Version/s: (was: v0.5.0) v0.5.1 > Create alert metadata based on application stream sink configuration > > > Key: EAGLE-493 > URL: https://issues.apache.org/jira/browse/EAGLE-493 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Minor > Fix For: v0.5.1 > > > When I integrate hdfs audit log application with alert engine, it looks > streams defined in applicationProvider.xml is not useful, because anyway we > have to define data source, stream, policy and publishment using alert API. > It is very difficult to convert streams in applicationProvider.xml to > metadata used by alert engine. > To achieve better user experience, we should create alert metadata > automatically when application is installed based on application stream sink. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-891) Add ApplicationPackageProvider Framework to support package multiple applications
[ https://issues.apache.org/jira/browse/EAGLE-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-891: - Fix Version/s: (was: v0.5.0) v0.5.1 > Add ApplicationPackageProvider Framework to support package multiple > applications > - > > Key: EAGLE-891 > URL: https://issues.apache.org/jira/browse/EAGLE-891 > Project: Eagle > Issue Type: Bug > Components: Core::App Engine >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.1 > > > Add ApplicationPackageProvider Framework to support package multiple > applications into one application pacackage, technically a > ApplicationPackageProvder is simply a ApplicationProvider but will package > the lifecycle management of different applications togather. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-452) Add Jersey Resource Unit Test Case
[ https://issues.apache.org/jira/browse/EAGLE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-452: - Fix Version/s: (was: v0.5.0) v0.5.1 > Add Jersey Resource Unit Test Case > -- > > Key: EAGLE-452 > URL: https://issues.apache.org/jira/browse/EAGLE-452 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.4.0, v0.5.0 >Reporter: Hao Chen >Assignee: Chang chen >Priority: Minor > Labels: unit-test > Fix For: v0.5.1 > > > We need to add more Unit Test Cases for Jersey Resources, referring to > https://github.com/apache/incubator-eagle/blob/develop/eagle-examples/eagle-app-example/src/test/java/org/apache/eagle/app/example/ExampleApplicationProviderTest.java#L45 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-522) Implement HOURLY_RULE for Absence Alert.
[ https://issues.apache.org/jira/browse/EAGLE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-522: - Fix Version/s: (was: v0.5.0) v0.5.1 > Implement HOURLY_RULE for Absence Alert. > > > Key: EAGLE-522 > URL: https://issues.apache.org/jira/browse/EAGLE-522 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Huizhi Lu >Assignee: Huizhi Lu > Fix For: v0.5.1 > > > Absence alert HOURLY_RULE is another use case for customers' needs. > We need to schedule jobs to be run every x hours. Current absence alert only > supports daily rule, but not our case. So HOURLY_RULE should be supported. > The policy for the hourly_rule should be like the following. > // "numOfFields, f1_name, f2_name, f1_value, f2_value, absenceWindowRuleType, > startTime, endTime, interval" > example: "1,jobID,job1,hourly_rule,2016-09-09 12:00:00,2016-09-09 > 13:00:00,10:00:00" > That being said, job1 starts during the period 2016-09-09 12:00:00 ~ > 2016-09-09 13:00:00, and the job should start again every 10:00:00 hours > after the period. > If not, absence alert will be triggered. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-552) Resolve eagle dependency security and license issues
[ https://issues.apache.org/jira/browse/EAGLE-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-552: - Fix Version/s: (was: v0.5.0) v0.5.1 > Resolve eagle dependency security and license issues > > > Key: EAGLE-552 > URL: https://issues.apache.org/jira/browse/EAGLE-552 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen >Priority: Trivial > Fix For: v0.5.1 > > > According to > https://www.versioneye.com/user/projects/57e0c46e18dd200012bcceec, Eagle > currently has 126 unique dependencies. 96 outdated. 3 unknown. > 5 known security vulnerabilities. We should resolve this warnings to make > sure eagle higher quality. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-381) Get resource manager version and improve app attempt id fetcher for spark job feeder
[
https://issues.apache.org/jira/browse/EAGLE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayesh updated EAGLE-381:
-
Fix Version/s: (was: v0.5.0)
v0.5.1
> Get resource manager version and improve app attempt id fetcher for spark job
> feeder
>
>
> Key: EAGLE-381
> URL: https://issues.apache.org/jira/browse/EAGLE-381
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Huizhi Lu
>Assignee: Huizhi Lu
> Fix For: v0.5.1
>
>
> About the attempt_id, assuming attempt_id starting from 1 may not be
> completely correct. This will not work in HDP Sandbox 2.4. Please see the
> attempt id in sandbox. Spark version is 1.6.0.
> I am confused why the attempt id are in different naming rule.
> We need to fix this issue. I will take care of it.
> hdp-2.4
> [ {
> "id" : "application_1468625664674_0003",
> "name" : "Spark Pi",
> "attempts" : [ {
> "attemptId" : "appattempt_1468625664674_0003_01",
> "startTime" : "2016-07-16T00:13:16.320GMT",
> "endTime" : "2016-07-16T00:13:24.279GMT",
> "sparkUser" : "spark",
> "completed" : true
> } ]
> }, {
> "id" : "application_1468625664674_0002",
> "name" : "Spark Pi",
> "attempts" : [ {
> "startTime" : "2016-07-16T00:12:01.386GMT",
> "endTime" : "2016-07-16T00:12:18.181GMT",
> "sparkUser" : "spark",
> "completed" : true
> } ]
> cluster.
> "id" : "application_1464382345557_264985",
> "name" : "",
> "attempts" : [ {
> "attemptId" : "1",
> "startTime" : "2016-07-15T09:01:25.032GMT",
> "endTime" : "2016-07-15T09:58:29.941GMT",
> "sparkUser" : "xxx",
> "completed" : true
> } ]
> solution:
> get resource manager version from api/conf and set attempt id depending on
> the version .
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (EAGLE-487) use guice module better in app framework
[ https://issues.apache.org/jira/browse/EAGLE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-487: - Fix Version/s: (was: v0.5.0) v0.5.1 > use guice module better in app framework > > > Key: EAGLE-487 > URL: https://issues.apache.org/jira/browse/EAGLE-487 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Edward Zhang >Assignee: Edward Zhang > Fix For: v0.5.1 > > > There are multiple issues with using guice module in app framework. > 1. ApplicationProviderServiceImpl is instantiated twice > 2. the interface between application and eagle server is not clear. It is not > correct to only let application to register submodules,, instead it should > includes some state inherited from eagle server, for example metadata storage > type. > 3. not necessary to use module scope, it is pretty over-engineering when > application only want to register some module. > 4. MemoryMetadataStore should use singleton -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-449) clean inner process alert engine code
[ https://issues.apache.org/jira/browse/EAGLE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-449: - Fix Version/s: (was: v0.5.0) v0.5.1 > clean inner process alert engine code > - > > Key: EAGLE-449 > URL: https://issues.apache.org/jira/browse/EAGLE-449 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Edward Zhang >Assignee: Edward Zhang > Fix For: v0.5.1 > > > alert engine now is separated into a standalone storm topology, it is not > necessary to keep inner process alert engine -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-809) Hide Kafka sink configuration used by alert engine
[ https://issues.apache.org/jira/browse/EAGLE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-809: - Fix Version/s: (was: v0.5.0) v0.5.1 > Hide Kafka sink configuration used by alert engine > -- > > Key: EAGLE-809 > URL: https://issues.apache.org/jira/browse/EAGLE-809 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.1 > > > * Hide Kafka topic creation used by alert engine > * Hide Kafka broker list used by alert engine -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-571) AlertEngine: Topology should support loopback topic created after policy deployed
[ https://issues.apache.org/jira/browse/EAGLE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-571: - Fix Version/s: (was: v0.5.0) v0.5.1 > AlertEngine: Topology should support loopback topic created after policy > deployed > - > > Key: EAGLE-571 > URL: https://issues.apache.org/jira/browse/EAGLE-571 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: v0.5.1 > > > when processing havetopic1 -> policy1 -> topic2; and topic2 -> policy2 > -> topic2 case, the topology is not able to start. Since the topic2 > initialization failure (topic2 not create yet) would make topic1 not able to > be consumed. Thus chicken-egg problem. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-234) Clean maven build warning in eagle
[ https://issues.apache.org/jira/browse/EAGLE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-234: - Fix Version/s: (was: v0.5.0) v0.5.1 > Clean maven build warning in eagle > -- > > Key: EAGLE-234 > URL: https://issues.apache.org/jira/browse/EAGLE-234 > Project: Eagle > Issue Type: New Feature >Reporter: Hao Chen >Assignee: Michael Wu > Labels: new > Fix For: v0.5.1 > > > clean warnings thrown out while compiling the project -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-853) Resolve eagle time problem on alert entities
[ https://issues.apache.org/jira/browse/EAGLE-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-853: - Fix Version/s: (was: v0.5.0) v0.5.1 > Resolve eagle time problem on alert entities > > > Key: EAGLE-853 > URL: https://issues.apache.org/jira/browse/EAGLE-853 > Project: Eagle > Issue Type: Bug > Components: Core::Alert Engine >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.1 > > > Resolve eagle time problem on alert entities > * Alert detail API should have time range instead of only "alertId" > * Add `/#/alert/detail/[alertId]?timestamp=[alertTime]` > * Fix alert detail url in alert email and alert list pages -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-623) [Maven] Move dependencies in profile "dev" to "eagle-topology-assembly"
[ https://issues.apache.org/jira/browse/EAGLE-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-623: - Fix Version/s: (was: v0.5.0) v0.5.1 > [Maven] Move dependencies in profile "dev" to "eagle-topology-assembly" > --- > > Key: EAGLE-623 > URL: https://issues.apache.org/jira/browse/EAGLE-623 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: wujinhu > Fix For: v0.5.1 > > > "dev" profile is just to make sure developer could easily load all apps in > development mode. So we should move all application-specific dependencies > into "eagle-topology-assembly" and let "eagle-server" depend on > "eagle-topology-assembly" in "dev" profile, and always keep > "eagle-topology-assembly" as single source of truth to assemble different > applications' topologies. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-793) Dropwizard related class not found exception in topology
[
https://issues.apache.org/jira/browse/EAGLE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayesh updated EAGLE-793:
-
Fix Version/s: (was: v0.5.0)
v0.5.1
> Dropwizard related class not found exception in topology
> -
>
> Key: EAGLE-793
> URL: https://issues.apache.org/jira/browse/EAGLE-793
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Priority: Minor
> Fix For: v0.5.1
>
>
> {code}
> 2016-11-15 04:46:28 eXtcos managed thread 1
> net.sf.extcos.internal.JavaResourceAccessor [ERROR] Unable to read interface
> [io.dropwizard.jersey.errors.LoggingExceptionMapper]
> java.io.IOException: Class not found
> at org.objectweb.asm.ClassReader.a(Unknown Source)
> [asm-all-5.0.jar:5.0]
> at org.objectweb.asm.ClassReader.(Unknown Source)
> [asm-all-5.0.jar:5.0]
> at
> net.sf.extcos.internal.JavaResourceAccessor.readSuperInterfaces(JavaResourceAccessor.java:446)
> [stormjar.jar:na]
> at
> net.sf.extcos.internal.JavaResourceAccessor.readInheritedInterfaces(JavaResourceAccessor.java:439)
> [stormjar.jar:na]
> at
> net.sf.extcos.internal.JavaResourceAccessor.readInterfaces(JavaResourceAccessor.java:431)
> [stormjar.jar:na]
> at
> net.sf.extcos.internal.JavaResourceAccessor.access$300(JavaResourceAccessor.java:38)
> [stormjar.jar:na]
> at
> net.sf.extcos.internal.JavaResourceAccessor$GeneralVisitor.visit(JavaResourceAccessor.java:90)
> [stormjar.jar:na]
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> [asm-all-5.0.jar:5.0]
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> [asm-all-5.0.jar:5.0]
> at
> net.sf.extcos.internal.JavaResourceAccessor.readClassData(JavaResourceAccessor.java:363)
> [stormjar.jar:na]
> at
> net.sf.extcos.internal.JavaResourceAccessor.setResourceUrl(JavaResourceAccessor.java:333)
> [stormjar.jar:na]
> at
> net.sf.extcos.internal.URLResource.getResourceAccessor(URLResource.java:93)
> [stormjar.jar:na]
> at net.sf.extcos.internal.URLResource.isClass(URLResource.java:126)
> [stormjar.jar:na]
> at net.sf.extcos.internal.RootFilter.filter(RootFilter.java:22)
> [stormjar.jar:na]
> at
> net.sf.extcos.internal.AbstractChainedFilter.filter(AbstractChainedFilter.java:89)
> [stormjar.jar:na]
> at
> net.sf.extcos.internal.ThreadingFilterInterceptor$1.run(ThreadingFilterInterceptor.java:48)
> [stormjar.jar:na]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
> 2016-11-15 04:46:28 eXtcos managed thread 1
> net.sf.extcos.internal.JavaResourceAccessor [ERROR] Unable to read super
> class [io.dropwizard.jersey.errors.LoggingExceptionMapper]
> java.io.IOException: Class not found
> at org.objectweb.asm.ClassReader.a(Unknown Source)
> [asm-all-5.0.jar:5.0]
> at org.objectweb.asm.ClassReader.(Unknown Source)
> [asm-all-5.0.jar:5.0]
> at
> net.sf.extcos.internal.JavaResourceAccessor.readSuperClasses(JavaResourceAccessor.java:392)
> [stormjar.jar:na]
> at
> net.sf.extcos.internal.JavaResourceAccessor.access$400(JavaResourceAccessor.java:38)
> [stormjar.jar:na]
> at
> net.sf.extcos.internal.JavaResourceAccessor$GeneralVisitor.visit(JavaResourceAccessor.java:91)
> [stormjar.jar:na]
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> [asm-all-5.0.jar:5.0]
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> [asm-all-5.0.jar:5.0]
> at
> net.sf.extcos.internal.JavaResourceAccessor.readClassData(JavaResourceAccessor.java:363)
> [stormjar.jar:na]
> at
> net.sf.extcos.internal.JavaResourceAccessor.setResourceUrl(JavaResourceAccessor.java:333)
> [stormjar.jar:na]
> at
> net.sf.extcos.internal.URLResource.getResourceAccessor(URLResource.java:93)
> [stormjar.jar:na]
> at net.sf.extcos.internal.URLResource.isClass(URLResource.java:126)
> [stormjar.jar:na]
> at net.sf.extcos.internal.RootFilter.filter(RootFilter.java:22)
> [stormjar.jar:na]
> at
> net.sf.extcos.internal.AbstractChainedFilter.filter(AbstractChainedFilter.java:89)
> [stormjar.jar:na]
> at
> net.sf.extcos.internal.ThreadingFilterInterceptor$1.run(ThreadingFilterInterceptor.java:48)
> [stormjar.jar:na]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
> 2016-11-15 04:46:28 eXtcos managed thread 1
> net.sf.extcos.internal.JavaResourceAccessor [ERROR] Unable to read interface
> [io.dropwizard.auth.basic.BasicAuthProvider]
> java.io.IOException: Class not found
> at org.objectweb.asm.ClassReader.a(Unknown Source)
> [asm-all-5.0.jar:5.0]
> at org.objectweb.asm.ClassReader.(Unknown Source)
> [asm-all-5.0.jar:5.0]
> at
>
[jira] [Updated] (EAGLE-540) Use Annotation to describe application metadata in ApplicationProvider.xml
[ https://issues.apache.org/jira/browse/EAGLE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-540: - Fix Version/s: (was: v0.5.0) v0.5.1 > Use Annotation to describe application metadata in ApplicationProvider.xml > -- > > Key: EAGLE-540 > URL: https://issues.apache.org/jira/browse/EAGLE-540 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.4.0 >Reporter: Hao Chen >Assignee: Hao Chen >Priority: Trivial > Fix For: v0.5.1 > > > Current application framework only supports to define application metadata in > XML descriptor file, it may be more convenient to define metadata directly > with Annotation in code. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-956) Metric Explorer and Customized Dashboard UI Part
[ https://issues.apache.org/jira/browse/EAGLE-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-956: - Fix Version/s: (was: v0.5.0) v0.5.1 > Metric Explorer and Customized Dashboard UI Part > > > Key: EAGLE-956 > URL: https://issues.apache.org/jira/browse/EAGLE-956 > Project: Eagle > Issue Type: Sub-task > Components: Core::UI Engine >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Jilin, Jiang > Fix For: v0.5.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-220) Add mvn script to handle maven dependency
[ https://issues.apache.org/jira/browse/EAGLE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-220: - Fix Version/s: (was: v0.5.0) v0.5.1 > Add mvn script to handle maven dependency > - > > Key: EAGLE-220 > URL: https://issues.apache.org/jira/browse/EAGLE-220 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.3.0 >Reporter: Hao Chen >Assignee: Hao Chen > Labels: Development > Fix For: v0.5.1 > > > Refer to https://github.com/apache/spark/blob/master/build/mvn -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-1025) bump version on master
[ https://issues.apache.org/jira/browse/EAGLE-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-1025: -- Fix Version/s: (was: v0.5.0) v0.5.1 > 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 > Fix For: v0.5.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-369) Improve eagle alert email template to provide more useful information and user experience
[ https://issues.apache.org/jira/browse/EAGLE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-369: - Fix Version/s: (was: v0.5.0) v0.5.1 > Improve eagle alert email template to provide more useful information and > user experience > - > > Key: EAGLE-369 > URL: https://issues.apache.org/jira/browse/EAGLE-369 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.3.1 >Reporter: Su Ralph >Assignee: Zhao, Qingwen > Fix For: v0.5.1 > > > From feedback: > (1) Time Stamp needs to be human readable. > (2) Consider capitalize wordings. > (3) What does lowNum and highNum mean here? Do they mean number of live > data nodes? How does this alert come out? Does that mean the current number > of live data nodes go above the highNum or below the lowNum? The lowNum > should display as “2,884” instead of “2884.0”. > (4) The Description field should always be there. If description is not > available, it should display as “Not provided by Policy Owner”. > (5) Should we consider displaying the name of the policy owner? That way, > people know whom to contact if they have question about the policy. > (6) The information in the Actions Required field is too generic and it is > not actionable. Can we do something about it? > (7) The text alignment (now always align center) may consider to align > left. Use want to make it look more professional. > (8) Text font is not consistent across the message. Should align to one > single font. Consider use Calibri as this is now the eBay official font > type. > (9) Lack of policy definition > The definition is > from every (e1 = hadoopJmxMetricEventStream[metric == > \"hadoop.namenode.fsnamesystemstate.numlivedatanodes\" ]) -> e2 = > hadoopJmxMetricEventStream[metric == e1.metric and host == e1.host and > (convert(e1.value, \"long\") - 2) >= convert(value, \"long\") ] within 5 min > select e1.metric, e1.host, e1.value as highNum, e1.timestamp as start, > e2.value as lowNum, e2.timestamp as end insert into tmp; > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-709) Document job performance monitoring application
[ https://issues.apache.org/jira/browse/EAGLE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-709: - Fix Version/s: (was: v0.5.0) v0.5.1 > Document job performance monitoring application > --- > > Key: EAGLE-709 > URL: https://issues.apache.org/jira/browse/EAGLE-709 > Project: Eagle > Issue Type: Task >Reporter: jianzhong.chen >Assignee: wujinhu > Labels: docuentation > Fix For: v0.5.1 > > > Application description along with: > - what to be monitored > - how to collect data, any expected impact to monitored service > - how to define a policy, especially on how to extract the fields from > stream? > - as much as supported policy examples > - latency expected for alert > - how to troubleshooting an application if any failure happens? > - .. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-669) Investigate eagle app metric system referring to https://github.com/ooyala/metrics_storm
[ https://issues.apache.org/jira/browse/EAGLE-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-669: - Fix Version/s: (was: v0.5.0) v0.5.1 > Investigate eagle app metric system referring to > https://github.com/ooyala/metrics_storm > > > Key: EAGLE-669 > URL: https://issues.apache.org/jira/browse/EAGLE-669 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen >Priority: Trivial > Fix For: v0.5.1 > > > Investigate eagle app metric system referring to > https://github.com/ooyala/metrics_storm -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-332) Build failed to due to [EAGLE-325]
[
https://issues.apache.org/jira/browse/EAGLE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayesh updated EAGLE-332:
-
Fix Version/s: (was: v0.5.0)
v0.5.1
> Build failed to due to [EAGLE-325]
> --
>
> Key: EAGLE-332
> URL: https://issues.apache.org/jira/browse/EAGLE-332
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Chang chen
> Labels: build
> Fix For: v0.5.1
>
>
> When building codes on develop branch after [EAGLE-329] ??Dependency
> incompatibility bug among jersey, asm and extcos under Java 8??, I get the
> following errors:
> {quote}
> [ERROR] Failed to execute goal on project alert-assembly: Could not resolve
> dependencies for project
> org.apache.eagle:alert-assembly:jar:0.5.0-incubating-SNAPSHOT: The following
> artifacts could not be resolved: org.apache.eagle:
> alert-coordinator:war:0.5.0-incubating-SNAPSHOT,
> org.apache.eagle:alert-metadata-service:war:0.5.0-incubating-SNAPSHOT:
> Failure to find
> org.apache.eagle:alert-coordinator:war:0.5.0-incubating-SNAPSHOT in
> http://repo.hortonworks.
> com/content/groups/public/ was cached in the local repository, resolution
> will not be reattempted until the update interval of hdp has elapsed or
> updates are forced -> [Help 1]
> {quote}
> It was introduced by EAGLE-325 which changed packaging type of
> alert-coordinator and alert-metadata-service from *war* to *jar*, but
> forgetted to update dependency in alert-assembly
> {code:xml}
>
> org.apache.eagle
> alert-coordinator
> ${project.version}
> war
>
>
> org.apache.eagle
> alert-metadata-service
> ${project.version}
> war
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (EAGLE-890) Add Job Scheduling Framework and HadoopHealthCheckApp
[ https://issues.apache.org/jira/browse/EAGLE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-890: - Fix Version/s: (was: v0.5.0) v0.5.1 > Add Job Scheduling Framework and HadoopHealthCheckApp > - > > Key: EAGLE-890 > URL: https://issues.apache.org/jira/browse/EAGLE-890 > Project: Eagle > Issue Type: New Feature > Components: Core::Job Engine >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.1 > > > Add Job Scheduling Framework and HadoopHealthCheckApp -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-542) Support @Bucket annotation in query engine
[ https://issues.apache.org/jira/browse/EAGLE-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-542: - Fix Version/s: (was: v0.5.0) v0.5.1 > Support @Bucket annotation in query engine > --- > > Key: EAGLE-542 > URL: https://issues.apache.org/jira/browse/EAGLE-542 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: wujinhu > Fix For: v0.5.1 > > > Eagle hbase scan takes 3 seconds fro 100k records which is because it scans > sequential TS rows. > We should resolve this problem to use eagle hbase as metric store. > As to eagle query engine, we maybe could simply add an annotation > @Bucket(Number) so that we could scan with buckets number of scanner > concurrently. > The storage guarantee is: > * Different bucket should be put into different region > * Better to have is these regions are separated into different region servers. > * Scan bucketed services with multiple concurrent scanner > * Merge & sort result. > Reference: > * https://github.com/sematext/HBaseWD > * http://opentsdb.net/docs/build/html/user_guide/writing.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-875) Fix hadoop.hbase.ipc.ipc.* metric to hadoop.hbase.regionserver.ipc.*
[ https://issues.apache.org/jira/browse/EAGLE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-875: - Fix Version/s: (was: v0.5.0) v0.5.1 > Fix hadoop.hbase.ipc.ipc.* metric to hadoop.hbase.regionserver.ipc.* > > > Key: EAGLE-875 > URL: https://issues.apache.org/jira/browse/EAGLE-875 > 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 > > > * Fix *hadoop.hbase.ipc.ipc.** metric to *hadoop.hbase.regionserver.ipc.** in > collector script > * Fix region server monitoring UI to use *hadoop.hbase.regionserver.ipc.** > instead of *hadoop.hbase.ipc.ipc.** -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-975) deploy site
[ https://issues.apache.org/jira/browse/EAGLE-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-975: - Fix Version/s: (was: v0.5.0) v0.5.1 > deploy site > --- > > Key: EAGLE-975 > URL: https://issues.apache.org/jira/browse/EAGLE-975 > 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-145) Send mail failed for javax.mail.internet.AddressException: Illegal semicolon, not in group
[
https://issues.apache.org/jira/browse/EAGLE-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayesh updated EAGLE-145:
-
Fix Version/s: (was: v0.5.0)
v0.5.1
> Send mail failed for javax.mail.internet.AddressException: Illegal semicolon,
> not in group
> --
>
> Key: EAGLE-145
> URL: https://issues.apache.org/jira/browse/EAGLE-145
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.1
>
>
> {code}
> 2016-02-02 02:52:03 o.a.e.p.e.PolicyProcessExecutor [INFO] Detected 1 alerts
> for policy missingBlockPolicy
> 2016-02-02 02:52:03 o.a.e.m.r.EagleServiceReporterMetricListener [INFO] Wrote
> 1 entities to service
> 2016-02-02 02:52:03 o.a.e.a.p.EaglePersist [INFO] Going to persist entities,
> type: AlertAPIEntity, list size: 1
> 2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] Initialized
> Thread-4-AlertNotificationExecutor_10: origin is :
> druid-test-host1-556191.slc01.dev.ebayc3.com(pid:14052), recipient of the
> email: li...@ebay.com;hch...@ebay.com, velocity TPL file: ALERT_DEFAULT.vm
> 2016-02-02 02:52:03 o.a.e.a.n.AlertEmailGenerator [INFO] Sending email in
> asynchronous to: h...@apache.org, cc: null
> 2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] Sending email, tried:
> 1, max: 3
> 2016-02-02 02:52:03 STDIO [INFO] DEBUG: setDebug: JavaMail version 1.4ea
> 2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] Env is: prod
> 2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] After calling
> generateCommonContext...
> 2016-02-02 02:52:03 o.a.velocity [ERROR] ResourceManager : unable to find
> resource 'templates/ALERT_DEFAULT.vm' in any resource loader.
> 2016-02-02 02:52:03 o.a.e.c.e.EagleMailClient [INFO] Send mail failed, got an
> AddressException: Illegal semicolon, not in group
> javax.mail.internet.AddressException: Illegal semicolon, not in group
> at javax.mail.internet.InternetAddress.parse(InternetAddress.java:780)
> ~[stormjar.jar:na]
> at javax.mail.internet.InternetAddress.parse(InternetAddress.java:555)
> ~[stormjar.jar:na]
> at javax.mail.internet.InternetAddress.parse(InternetAddress.java:532)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.common.email.EagleMailClient._send(EagleMailClient.java:104)
> [stormjar.jar:na]
> at
> org.apache.eagle.common.email.EagleMailClient.send(EagleMailClient.java:167)
> [stormjar.jar:na]
> at
> org.apache.eagle.common.email.EagleMailClient.send(EagleMailClient.java:187)
> [stormjar.jar:na]
> at
> org.apache.eagle.common.email.EagleMailClient.send(EagleMailClient.java:193)
> [stormjar.jar:na]
> at
> org.apache.eagle.alert.common.AlertEmailSender.run(AlertEmailSender.java:129)
> [stormjar.jar:na]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> [na:1.7.0_60]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> [na:1.7.0_60]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [na:1.7.0_60]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [na:1.7.0_60]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]
> 2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] Success of sending
> email: false
> 2016-02-02 02:52:03 o.a.e.a.c.AlertEmailSender [INFO] Sleep for a while
> before retrying
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (EAGLE-922) Integrate role-based Authentication in API
[ https://issues.apache.org/jira/browse/EAGLE-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-922: - Fix Version/s: (was: v0.5.0) v0.5.1 > Integrate role-based Authentication in API > -- > > Key: EAGLE-922 > URL: https://issues.apache.org/jira/browse/EAGLE-922 > Project: Eagle > Issue Type: Sub-task > Components: Core::Eagle Server >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.1 > > > Integrate role-based Authentication in API -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-676) Package hadoop jmx metric collector into eagle pacakge
[ https://issues.apache.org/jira/browse/EAGLE-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-676: - Fix Version/s: (was: v0.5.0) v0.5.1 > Package hadoop jmx metric collector into eagle pacakge > -- > > Key: EAGLE-676 > URL: https://issues.apache.org/jira/browse/EAGLE-676 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.1 > > > Package hadoop jmx metric collector into eagle pacakge -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-626) Add Eagle HBase Metric Store Publisher
[ https://issues.apache.org/jira/browse/EAGLE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-626: - Fix Version/s: (was: v0.5.0) v0.5.1 > Add Eagle HBase Metric Store Publisher > -- > > Key: EAGLE-626 > URL: https://issues.apache.org/jira/browse/EAGLE-626 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-469) make dataSource configuration extremely simple
[
https://issues.apache.org/jira/browse/EAGLE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayesh updated EAGLE-469:
-
Fix Version/s: (was: v0.5.0)
v0.5.1
> make dataSource configuration extremely simple
> --
>
> Key: EAGLE-469
> URL: https://issues.apache.org/jira/browse/EAGLE-469
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
> Fix For: v0.5.1
>
>
> Today dataSource configuration is very cumbersome, we actually can reduce
> significantly the size of config entries as most of configurations use the
> default values.
> "dataSourceConfig": {
> "topic" : "sandbox_hbase_security_log",
> "zkConnection" : "sandbox.hortonworks.com:2181",
> "zkConnectionTimeoutMS" : 15000,
> "consumerGroupId" : "EagleConsumer",
> "fetchSize" : 1048586,
> "deserializerClass" :
> "org.apache.eagle.security.hbase.HbaseAuditLogKafkaDeserializer",
> "transactionZKServers" : "sandbox.hortonworks.com",
> "transactionZKPort" : 2181,
> "transactionZKRoot" : "/consumers",
> "consumerGroupId" : "eagle.hbasesecurity.consumer",
> "transactionStateUpdateMS" : 2000
> }
> The new data source config would be like:
> "dataSourceConfig": {
> "topic" : "hbase_audit_log",
> "zkConnection" : "server.eagle.apache.org:2181",
> "txZkServers" : "server.eagle.apache.org:2181",
> "schemeCls" : "storm.kafka.StringScheme"
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (EAGLE-468) clean up eagle-application-service to be replaced by new app framework
[ https://issues.apache.org/jira/browse/EAGLE-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-468: - Fix Version/s: (was: v0.5.0) v0.5.1 > clean up eagle-application-service to be replaced by new app framework > -- > > Key: EAGLE-468 > URL: https://issues.apache.org/jira/browse/EAGLE-468 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Edward Zhang >Assignee: Edward Zhang >Priority: Minor > Fix For: v0.5.1 > > > application service provides web resources for managing storm topology > remotely, this is replaced by new app framework. > But in new app framework, we still need investigate how to monitor > application status. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-678) Support to configure links for site
[ https://issues.apache.org/jira/browse/EAGLE-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-678: - Fix Version/s: (was: v0.5.0) v0.5.1 > Support to configure links for site > --- > > Key: EAGLE-678 > URL: https://issues.apache.org/jira/browse/EAGLE-678 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.1 > > > Support to configure links for site. > As to Hadoop, support set: > * Name Node URL > * Resource Manager URL > As to HBase, support: > * HBase master URL > Spark: > * Spark History Server URL -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-645) No log retention for eagle server log
[ https://issues.apache.org/jira/browse/EAGLE-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-645: - Fix Version/s: (was: v0.5.0) v0.5.1 > No log retention for eagle server log > - > > Key: EAGLE-645 > URL: https://issues.apache.org/jira/browse/EAGLE-645 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen > Fix For: v0.5.1 > > > There is not any retention configurations in Eagle server. The logs keeps > increasing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-388) Alerting on any customized kafka data source (topic)
[ https://issues.apache.org/jira/browse/EAGLE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-388: - Fix Version/s: (was: v0.5.0) v0.5.1 > Alerting on any customized kafka data source (topic) > - > > Key: EAGLE-388 > URL: https://issues.apache.org/jira/browse/EAGLE-388 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.4.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.1 > > > Alerting on any customized kafka data source (topic) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (EAGLE-772) simply refactor mr running job feeder
[ https://issues.apache.org/jira/browse/EAGLE-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh updated EAGLE-772: - Fix Version/s: (was: v0.5.0) v0.5.1 > simply refactor mr running job feeder > - > > Key: EAGLE-772 > URL: https://issues.apache.org/jira/browse/EAGLE-772 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.1 > > > Currently, both MRRunningJobFetchSpout and MRRunningJobParseBolt try to > delete application from zookeeper, the two threads probably delete the same > applications. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
