[jira] [Created] (EAGLE-846) HDFS Audit log traffic monitoring
Zhao, Qingwen created EAGLE-846: --- Summary: HDFS Audit log traffic monitoring Key: EAGLE-846 URL: https://issues.apache.org/jira/browse/EAGLE-846 Project: Eagle Issue Type: New Feature Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Fix For: v0.5.0 HDFS Audit log traffic monitoring -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-834) Add Daily Job Summery Report
Zhao, Qingwen created EAGLE-834: --- Summary: Add Daily Job Summery Report Key: EAGLE-834 URL: https://issues.apache.org/jira/browse/EAGLE-834 Project: Eagle Issue Type: New Feature Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen * Extend Application framework to support application to register ManagedTask into eagle server (refer to Application HealthCheck registry approach) * Register a daily job report task to MRJobApplication. * Add configurations in application to control the behavior: * Daily job report enable/disable * Report receipt email address * Report frequency (24 hour by default) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-829) refactor PublishmentType model to align with PolicyDefinition
Zhao, Qingwen created EAGLE-829: --- Summary: refactor PublishmentType model to align with PolicyDefinition Key: EAGLE-829 URL: https://issues.apache.org/jira/browse/EAGLE-829 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Priority: Minor Fix For: v0.5.0 rename fields: className -> name -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-819) Data From Topology Health Check are inaccurate
Zhao, Qingwen created EAGLE-819: --- Summary: Data From Topology Health Check are inaccurate Key: EAGLE-819 URL: https://issues.apache.org/jira/browse/EAGLE-819 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Fix For: v0.5.0 1. data overflow 2. data generated by yarn crawler are inaccurate -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-818) CEP Based Aggregate Framework
Zhao, Qingwen created EAGLE-818: --- Summary: CEP Based Aggregate Framework Key: EAGLE-818 URL: https://issues.apache.org/jira/browse/EAGLE-818 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Fix For: v0.5.0 Implementation of CEP based aggregate framework -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-811) Refactor table of alert engine metadata
Zhao, Qingwen created EAGLE-811: --- Summary: Refactor table of alert engine metadata Key: EAGLE-811 URL: https://issues.apache.org/jira/browse/EAGLE-811 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Fix For: v0.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-809) Hide Kafka sink configuration used by alert engine
Zhao, Qingwen created EAGLE-809: --- Summary: Hide Kafka sink configuration used by alert engine Key: EAGLE-809 URL: https://issues.apache.org/jira/browse/EAGLE-809 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Fix For: v0.5.0 * Hide Kafka topic creation used by alert engine * Hide Kafka broker list used by alert engine -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-803) Just save latest N schedule_state in eagle database.
Zhao, Qingwen created EAGLE-803: --- Summary: Just save latest N schedule_state in eagle database. Key: EAGLE-803 URL: https://issues.apache.org/jira/browse/EAGLE-803 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Fix For: v0.5.0 schedule_state table increases with the metadata updates. In this way, quite a lot of old state occupy the space of database. For eagle, it is enough to just save latest N schedule_state in eagle database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-798) Add a new alert publisher to store alerts into hbase
Zhao, Qingwen created EAGLE-798: --- Summary: Add a new alert publisher to store alerts into hbase Key: EAGLE-798 URL: https://issues.apache.org/jira/browse/EAGLE-798 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Priority: Minor Fix For: v0.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-793) Dropwizard related class not found exception in topology
Zhao, Qingwen created EAGLE-793:
---
Summary: 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.0
{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
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
[jira] [Created] (EAGLE-789) Add a new publisher to write alerts into a local file
Zhao, Qingwen created EAGLE-789: --- Summary: Add a new publisher to write alerts into a local file Key: EAGLE-789 URL: https://issues.apache.org/jira/browse/EAGLE-789 Project: Eagle Issue Type: New Feature Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Fix For: v0.5.0 Add a new publisher to write alerts into a local file -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-780) Update spark running config to integrate with the application framework
Zhao, Qingwen created EAGLE-780: --- Summary: Update spark running config to integrate with the application framework Key: EAGLE-780 URL: https://issues.apache.org/jira/browse/EAGLE-780 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Fix For: v0.5.0 Update spark running config to integrate with the application framework -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-646) AlertUnitTopology does not rebuild the scheduler state after restarting
[ https://issues.apache.org/jira/browse/EAGLE-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-646. --- Resolution: Fixed Fix Version/s: v0.5.0 > AlertUnitTopology does not rebuild the scheduler state after restarting > --- > > Key: EAGLE-646 > URL: https://issues.apache.org/jira/browse/EAGLE-646 > Project: Eagle > Issue Type: Bug >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > > AlertUnitTopology does not rebuild the scheduler state after restarting, > which leads to messages fail frequently if users change the topology > configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-545) hdfs/bhase/yarn health check
[ https://issues.apache.org/jira/browse/EAGLE-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-545. --- Resolution: Done > hdfs/bhase/yarn health check > - > > Key: EAGLE-545 > URL: https://issues.apache.org/jira/browse/EAGLE-545 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > The app aims to monitor those services with a master-slave structured > topology, and provides metrics at the HOST level. Specifically, this app will > support the following services healthy check > * HDFS: namenode, datanode, journalnode > * HBASE: hmaster, regionservers > * YARN: resourcemanager, nodemanagers, historyserver > More detailed requirements: > 1. provides node level health diagnosis including the master nodes and slave > nodes > 2. provide several cluster-level metrics -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-712) Document HDFS audit log monitoring application (DAM)
[ https://issues.apache.org/jira/browse/EAGLE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-712. --- Resolution: Done > Document HDFS audit log monitoring application (DAM) > > > Key: EAGLE-712 > URL: https://issues.apache.org/jira/browse/EAGLE-712 > Project: Eagle > Issue Type: Task >Reporter: jianzhong.chen >Assignee: Zhao, Qingwen > Labels: docuentation > Fix For: v0.5.0 > > > 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.3.4#6332)
[jira] [Created] (EAGLE-763) Clear ScheduleState table in Mysql periodically
Zhao, Qingwen created EAGLE-763: --- Summary: Clear ScheduleState table in Mysql periodically Key: EAGLE-763 URL: https://issues.apache.org/jira/browse/EAGLE-763 Project: Eagle Issue Type: Improvement Reporter: Zhao, Qingwen ScheduleState table in mysql is increasing with no deletion operation provided. Eagle should clear the old data periodically to avoid data explosion -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-744) add a new rest api to filter alerts by policy id
[
https://issues.apache.org/jira/browse/EAGLE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen closed EAGLE-744.
---
Resolution: Fixed
> add a new rest api to filter alerts by policy id
>
>
> Key: EAGLE-744
> URL: https://issues.apache.org/jira/browse/EAGLE-744
> Project: Eagle
> Issue Type: Improvement
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> Add a new rest api for seaching an alert by policy id
> GET /rest/metadata/policies/\{policyId\}/alerts
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (EAGLE-743) StreamRouter fails to modify the routing map
[ https://issues.apache.org/jira/browse/EAGLE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-743. --- Resolution: Fixed > StreamRouter fails to modify the routing map > > > Key: EAGLE-743 > URL: https://issues.apache.org/jira/browse/EAGLE-743 > Project: Eagle > Issue Type: Bug >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > When the policy parallelism hint is changed, the schedule states can be > correctly generated. While the topology routing map still is the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-760) Policy alert list support size limit
[
https://issues.apache.org/jira/browse/EAGLE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen closed EAGLE-760.
---
Resolution: Fixed
> Policy alert list support size limit
>
>
> Key: EAGLE-760
> URL: https://issues.apache.org/jira/browse/EAGLE-760
> Project: Eagle
> Issue Type: Improvement
>Reporter: Jilin, Jiang
>Assignee: Zhao, Qingwen
>Priority: Minor
>
> GET /rest/metadata/policies/\{policyId\}/alerts?size=1000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (EAGLE-761) Data skews in KafakStreamSink
[ https://issues.apache.org/jira/browse/EAGLE-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-761. --- Resolution: Fixed > Data skews in KafakStreamSink > - > > Key: EAGLE-761 > URL: https://issues.apache.org/jira/browse/EAGLE-761 > Project: Eagle > Issue Type: Bug >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > When data skews in Kafka sink topic, the alert engine may consumes the data > evenly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-751) Two policyDefinitions with different status are equal
[ https://issues.apache.org/jira/browse/EAGLE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-751. --- Resolution: Fixed > Two policyDefinitions with different status are equal > -- > > Key: EAGLE-751 > URL: https://issues.apache.org/jira/browse/EAGLE-751 > Project: Eagle > Issue Type: Bug >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > In equal() of PolicyDefinition, field policyStatus is missed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-760) Policy alert list support size limit
[
https://issues.apache.org/jira/browse/EAGLE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-760:
Description: GET /rest/metadata/policies/\{policyId\}/alerts?size=1000
(was: GET /rest/metadata/policies/{policyId}/alerts?size=1000)
> Policy alert list support size limit
>
>
> Key: EAGLE-760
> URL: https://issues.apache.org/jira/browse/EAGLE-760
> Project: Eagle
> Issue Type: Improvement
>Reporter: Jilin, Jiang
>Assignee: Zhao, Qingwen
>Priority: Minor
>
> GET /rest/metadata/policies/\{policyId\}/alerts?size=1000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (EAGLE-761) Data skews in KafakStreamSink
Zhao, Qingwen created EAGLE-761: --- Summary: Data skews in KafakStreamSink Key: EAGLE-761 URL: https://issues.apache.org/jira/browse/EAGLE-761 Project: Eagle Issue Type: Bug Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen When data skews in Kafka sink topic, the alert engine may consumes the data evenly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-751) Two policyDefinitions with different status are equal
Zhao, Qingwen created EAGLE-751: --- Summary: Two policyDefinitions with different status are equal Key: EAGLE-751 URL: https://issues.apache.org/jira/browse/EAGLE-751 Project: Eagle Issue Type: Bug Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen In equal() of PolicyDefinition, field policyStatus is missed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-744) add a new rest api to filter alerts by policy id
[
https://issues.apache.org/jira/browse/EAGLE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-744:
Description:
Add a new rest api for seaching an alert by policy id
GET /rest/metadata/policies/\{policyId\}/alerts
was:
Add a new rest api for seaching an alert by policy id
GET /rest/metadata/policies/{policyId}/alerts
> add a new rest api to filter alerts by policy id
>
>
> Key: EAGLE-744
> URL: https://issues.apache.org/jira/browse/EAGLE-744
> Project: Eagle
> Issue Type: Improvement
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> Add a new rest api for seaching an alert by policy id
> GET /rest/metadata/policies/\{policyId\}/alerts
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-744) add a new rest api to filter alerts by policy id
[
https://issues.apache.org/jira/browse/EAGLE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-744:
Description:
Add a new rest api for seaching an alert by policy id
GET /rest/metadata/policies/{policyId}/alerts
was:
Add a new rest api for seaching an alert by policy id
GET /rest/metadata/alerts/{policyId}
> add a new rest api to filter alerts by policy id
>
>
> Key: EAGLE-744
> URL: https://issues.apache.org/jira/browse/EAGLE-744
> Project: Eagle
> Issue Type: Improvement
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> Add a new rest api for seaching an alert by policy id
> GET /rest/metadata/policies/{policyId}/alerts
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-744) add a new rest api to filter alerts by policy id
[
https://issues.apache.org/jira/browse/EAGLE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-744:
Description:
Add a new rest api for seaching an alert by policy id
GET /rest/metadata/policies/{policyId}/alerts
was:
Add a new rest api for seaching an alert by policy id
GET /rest/metadata/policies/{policyId}/alerts
> add a new rest api to filter alerts by policy id
>
>
> Key: EAGLE-744
> URL: https://issues.apache.org/jira/browse/EAGLE-744
> Project: Eagle
> Issue Type: Improvement
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> Add a new rest api for seaching an alert by policy id
> GET /rest/metadata/policies/{policyId}/alerts
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (EAGLE-744) add a new rest api to filter alerts by policy id
Zhao, Qingwen created EAGLE-744:
---
Summary: add a new rest api to filter alerts by policy id
Key: EAGLE-744
URL: https://issues.apache.org/jira/browse/EAGLE-744
Project: Eagle
Issue Type: Improvement
Reporter: Zhao, Qingwen
Assignee: Zhao, Qingwen
Add a new rest api for seaching an alert by policy id
GET /rest/metadata/alerts/{policyId}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (EAGLE-743) StreamRouter fails to modify the routing map
Zhao, Qingwen created EAGLE-743: --- Summary: StreamRouter fails to modify the routing map Key: EAGLE-743 URL: https://issues.apache.org/jira/browse/EAGLE-743 Project: Eagle Issue Type: Bug Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen When the policy parallelism hint is changed, the schedule states can be correctly generated. While the topology routing map still is the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-704) Update spark history config to integrate with the new application framework
[ https://issues.apache.org/jira/browse/EAGLE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-704. --- Resolution: Fixed > Update spark history config to integrate with the new application framework > --- > > Key: EAGLE-704 > URL: https://issues.apache.org/jira/browse/EAGLE-704 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > This ticket will update SparkHistoryJobAppProvider.xml to integrate with > application framework. In this way, users can manage this topology on the web -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-637) Set router/alert task number of UnitTopologyRunner
[ https://issues.apache.org/jira/browse/EAGLE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-637. --- Resolution: Fixed > Set router/alert task number of UnitTopologyRunner > -- > > Key: EAGLE-637 > URL: https://issues.apache.org/jira/browse/EAGLE-637 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > In UnitTopologyRunner, the router/alert bolt task number is not set. The > default value is 1. While in some cases, if the task number is not 1, then > the logical is wrong. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-721) Remove duplicate DataTimeUtil class
[ https://issues.apache.org/jira/browse/EAGLE-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-721. --- Resolution: Fixed > Remove duplicate DataTimeUtil class > > > Key: EAGLE-721 > URL: https://issues.apache.org/jira/browse/EAGLE-721 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > DateTimeUtil class exists in two different packages: org.apache.eagle.common > and org.apache.eagle.alert.utils > Both of them are used in the code, and they have different timeZone. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-721) Remove duplicate DataTimeUtil class
Zhao, Qingwen created EAGLE-721: --- Summary: Remove duplicate DataTimeUtil class Key: EAGLE-721 URL: https://issues.apache.org/jira/browse/EAGLE-721 Project: Eagle Issue Type: Improvement Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen DateTimeUtil class exists in two different packages: org.apache.eagle.common and org.apache.eagle.alert.utils Both of them are used in the code, and they have different timeZone. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-681) Add new publisher AlertEagleStorePlugin
[ https://issues.apache.org/jira/browse/EAGLE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-681. --- Resolution: Done > Add new publisher AlertEagleStorePlugin > > > Key: EAGLE-681 > URL: https://issues.apache.org/jira/browse/EAGLE-681 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > > In Eagle 0.5, only three types of publishers supported: email, kafka, slack. > Users may be want to view all the alerts on the web, which requires eagle to > store the alert into database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-696) Improve HdfsAuditLogApplication & AlertUnitTopologyApp config
[ https://issues.apache.org/jira/browse/EAGLE-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-696: Description: add field display name & refactor the configuration (was: add field display name & refactor the configuration organization) > Improve HdfsAuditLogApplication & AlertUnitTopologyApp config > -- > > Key: EAGLE-696 > URL: https://issues.apache.org/jira/browse/EAGLE-696 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > add field display name & refactor the configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-696) Improve HdfsAuditLogApplication & AlertUnitTopologyApp config
[ https://issues.apache.org/jira/browse/EAGLE-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-696: Description: add field display name & refactor the configuration organization > Improve HdfsAuditLogApplication & AlertUnitTopologyApp config > -- > > Key: EAGLE-696 > URL: https://issues.apache.org/jira/browse/EAGLE-696 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > add field display name & refactor the configuration organization -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-681) Add new publisher AlertEagleStorePlugin
Zhao, Qingwen created EAGLE-681: --- Summary: Add new publisher AlertEagleStorePlugin Key: EAGLE-681 URL: https://issues.apache.org/jira/browse/EAGLE-681 Project: Eagle Issue Type: New Feature Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Fix For: v0.5.0 In Eagle 0.5, only three types of publishers supported: email, kafka, slack. Users may be want to view all the alerts on the web, which requires eagle to store the alert into database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-645) No log retention for eagle server log
Zhao, Qingwen created EAGLE-645: --- Summary: 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.0 There is not any retention configurations in Eagle server. The logs keeps increasing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-637) Set router/alert task number of UnitTopologyRunner
Zhao, Qingwen created EAGLE-637: --- Summary: Set router/alert task number of UnitTopologyRunner Key: EAGLE-637 URL: https://issues.apache.org/jira/browse/EAGLE-637 Project: Eagle Issue Type: Improvement Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen In UnitTopologyRunner, the router/alert bolt task number is not set. The default value is 1. While in some cases, if the task number is not 1, then the logical is wrong. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-592) Add a hdfs audit log parser which consumes message in Json format
[
https://issues.apache.org/jira/browse/EAGLE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-592:
Description:
In Hdfs audit log application, the default deserializer class configured in
Eagle is "storm.kafka.StringScheme", which only processes the raw log
{code}
"dataSourceConfig": {
...
"schemeCls" : "storm.kafka.StringScheme"
},
{code}
For some log collector agents, like filebeat (5.0), the output is in json
format.
{"xx": "abc", "yy": "aabbcc", "message": "audit log"}
This ticket will create a class MessageJsonScheme which will extract 'message'
field from the message from Kafka
was:
For some log collector agents, like filebeat (5.0), the output is in json
format.
{"xx": "abc", "yy": "aabbcc", "message": "audit log"}
This ticket will create a class MessageJsonScheme which will extract 'message'
field from the message from Kafka
> Add a hdfs audit log parser which consumes message in Json format
> -
>
> Key: EAGLE-592
> URL: https://issues.apache.org/jira/browse/EAGLE-592
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> In Hdfs audit log application, the default deserializer class configured in
> Eagle is "storm.kafka.StringScheme", which only processes the raw log
> {code}
> "dataSourceConfig": {
> ...
> "schemeCls" : "storm.kafka.StringScheme"
> },
> {code}
> For some log collector agents, like filebeat (5.0), the output is in json
> format.
> {"xx": "abc", "yy": "aabbcc", "message": "audit log"}
> This ticket will create a class MessageJsonScheme which will extract
> 'message' field from the message from Kafka
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (EAGLE-592) Add a hdfs audit log parser which consumes message in Json format
[
https://issues.apache.org/jira/browse/EAGLE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen closed EAGLE-592.
---
Resolution: Done
> Add a hdfs audit log parser which consumes message in Json format
> -
>
> Key: EAGLE-592
> URL: https://issues.apache.org/jira/browse/EAGLE-592
> Project: Eagle
> Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> In Hdfs audit log application, the default deserializer class configured in
> Eagle is "storm.kafka.StringScheme", which only processes the raw log
> {code}
> "dataSourceConfig": {
> ...
> "schemeCls" : "storm.kafka.StringScheme"
> },
> {code}
> For some log collector agents, like filebeat (5.0), the output is in json
> format.
> {"xx": "abc", "yy": "aabbcc", "message": "audit log"}
> This ticket will create a class MessageJsonScheme which will extract
> 'message' field from the message from Kafka
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (EAGLE-253) query=AlertService[@hostname=~".*"] returns different results under HBASE and JDBC DB
[ https://issues.apache.org/jira/browse/EAGLE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-253. --- Resolution: Not A Problem > query=AlertService[@hostname=~".*"] returns different results under HBASE and > JDBC DB > - > > Key: EAGLE-253 > URL: https://issues.apache.org/jira/browse/EAGLE-253 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.3.0 > Environment: when AlertAPIEntity#host is null, the expected result is > a empty list. But the query on HBASE can ignore this condition, and gives the > results satisfying other conditions >Reporter: Zhao, Qingwen > Fix For: v0.5.0 > > > when AlertAPIEntity#host is null, the expected result is a empty list. But > the query on HBASE can ignore this condition, and gives the results > satisfying other conditions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-609) NullPointerException in DefaultDeduplicator
Zhao, Qingwen created EAGLE-609:
---
Summary: NullPointerException in DefaultDeduplicator
Key: EAGLE-609
URL: https://issues.apache.org/jira/browse/EAGLE-609
Project: Eagle
Issue Type: Bug
Affects Versions: 0.5
Reporter: Zhao, Qingwen
Assignee: Zhao, Qingwen
Fix For: 0.5
{code}
// make all of the field as unique key if no custom dedup field provided
if (customDedupFields == null || customDedupFields.size() <= 0) {
customFieldValues.put(colName, event.getData()[i].toString());
} else {
for (String field : customDedupFields) {
if (colName.equals(field)) {
customFieldValues.put(field,
event.getData()[i].toString());
break;
}
}
}
{code}
In the above code, if the value of colName is null, then nullPointerException
is thrown
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (EAGLE-271) Topology management in remote mode including start/stop/status operations
[ https://issues.apache.org/jira/browse/EAGLE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-271. --- Resolution: Done > Topology management in remote mode including start/stop/status operations > - > > Key: EAGLE-271 > URL: https://issues.apache.org/jira/browse/EAGLE-271 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.4.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.4.0 > > > Users can submit a topology to a remote Storm cluster on the Eagle UI, as > well as stop it -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-271) Topology management in remote mode including start/stop/status operations
[ https://issues.apache.org/jira/browse/EAGLE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-271: Description: Users can submit a topology to a remote Storm cluster on the Eagle UI, as well as stop it > Topology management in remote mode including start/stop/status operations > - > > Key: EAGLE-271 > URL: https://issues.apache.org/jira/browse/EAGLE-271 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.4.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.4.0 > > > Users can submit a topology to a remote Storm cluster on the Eagle UI, as > well as stop it -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (EAGLE-271) Topology management in remote mode including start/stop/status operations
[ https://issues.apache.org/jira/browse/EAGLE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen reopened EAGLE-271: - > Topology management in remote mode including start/stop/status operations > - > > Key: EAGLE-271 > URL: https://issues.apache.org/jira/browse/EAGLE-271 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.4.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-372) Change AlertNotificationEntity#fields type from String to List
[ https://issues.apache.org/jira/browse/EAGLE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-372. --- Resolution: Not A Problem > Change AlertNotificationEntity#fields type from String to List > --- > > Key: EAGLE-372 > URL: https://issues.apache.org/jira/browse/EAGLE-372 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > > We should avoid using String to express complex type in the entity definition. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-372) Change AlertNotificationEntity#fields type from String to List
[ https://issues.apache.org/jira/browse/EAGLE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-372: Description: We should avoid using String to express complex type in the entity definition. > Change AlertNotificationEntity#fields type from String to List > --- > > Key: EAGLE-372 > URL: https://issues.apache.org/jira/browse/EAGLE-372 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > > We should avoid using String to express complex type in the entity definition. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (EAGLE-372) Change AlertNotificationEntity#fields type from String to List
[ https://issues.apache.org/jira/browse/EAGLE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen reopened EAGLE-372: - > Change AlertNotificationEntity#fields type from String to List > --- > > Key: EAGLE-372 > URL: https://issues.apache.org/jira/browse/EAGLE-372 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-351) Running queue metrics monitoring
[
https://issues.apache.org/jira/browse/EAGLE-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen closed EAGLE-351.
---
Resolution: Duplicate
> Running queue metrics monitoring
> -
>
> Key: EAGLE-351
> URL: https://issues.apache.org/jira/browse/EAGLE-351
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> Hadoop running queue monitoring aims to collect some queue related metrics.
> Currently we only fetch data from the following three apis.
> CLUSTER_SCHEDULER_URL = "ws/v1/cluster/scheduler"
> CLUSTER_METRICS_URL = "ws/v1/cluster/metrics"
> CLUSTER_RUNNING_APPS_URL = "ws/v1/cluster/apps?state=RUNNING"
> Sample queries
> http://localhost:9098/eagle-service/rest/entities?query=RunningQueueService[@site="sandbox"]{*}=1000
> http://localhost:9098/eagle-service/rest/entities?query=GenericMetricService[@site="sandbox"]{*}=hadoop.queue.usedcapacity=1000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (EAGLE-351) Running queue metrics monitoring
[ https://issues.apache.org/jira/browse/EAGLE-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen reopened EAGLE-351: - > Running queue metrics monitoring > - > > Key: EAGLE-351 > URL: https://issues.apache.org/jira/browse/EAGLE-351 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-351) Running queue metrics monitoring
[
https://issues.apache.org/jira/browse/EAGLE-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15557513#comment-15557513
]
Zhao, Qingwen commented on EAGLE-351:
-
This ticket is duplicated. I will close it
> Running queue metrics monitoring
> -
>
> Key: EAGLE-351
> URL: https://issues.apache.org/jira/browse/EAGLE-351
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> Hadoop running queue monitoring aims to collect some queue related metrics.
> Currently we only fetch data from the following three apis.
> CLUSTER_SCHEDULER_URL = "ws/v1/cluster/scheduler"
> CLUSTER_METRICS_URL = "ws/v1/cluster/metrics"
> CLUSTER_RUNNING_APPS_URL = "ws/v1/cluster/apps?state=RUNNING"
> Sample queries
> http://localhost:9098/eagle-service/rest/entities?query=RunningQueueService[@site="sandbox"]{*}=1000
> http://localhost:9098/eagle-service/rest/entities?query=GenericMetricService[@site="sandbox"]{*}=hadoop.queue.usedcapacity=1000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-351) Running queue metrics monitoring
[
https://issues.apache.org/jira/browse/EAGLE-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-351:
Description:
Hadoop running queue monitoring aims to collect some queue related metrics.
Currently we only fetch data from the following three apis.
CLUSTER_SCHEDULER_URL = "ws/v1/cluster/scheduler"
CLUSTER_METRICS_URL = "ws/v1/cluster/metrics"
CLUSTER_RUNNING_APPS_URL = "ws/v1/cluster/apps?state=RUNNING"
Sample queries
http://localhost:9098/eagle-service/rest/entities?query=RunningQueueService[@site="sandbox"]{*}=1000
http://localhost:9098/eagle-service/rest/entities?query=GenericMetricService[@site="sandbox"]{*}=hadoop.queue.usedcapacity=1000
> Running queue metrics monitoring
> -
>
> Key: EAGLE-351
> URL: https://issues.apache.org/jira/browse/EAGLE-351
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> Hadoop running queue monitoring aims to collect some queue related metrics.
> Currently we only fetch data from the following three apis.
> CLUSTER_SCHEDULER_URL = "ws/v1/cluster/scheduler"
> CLUSTER_METRICS_URL = "ws/v1/cluster/metrics"
> CLUSTER_RUNNING_APPS_URL = "ws/v1/cluster/apps?state=RUNNING"
> Sample queries
> http://localhost:9098/eagle-service/rest/entities?query=RunningQueueService[@site="sandbox"]{*}=1000
> http://localhost:9098/eagle-service/rest/entities?query=GenericMetricService[@site="sandbox"]{*}=hadoop.queue.usedcapacity=1000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-42) Customized partition support for Kafka spout
[ https://issues.apache.org/jira/browse/EAGLE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-42: --- Description: This is not a issue any more. I will close this ticket > Customized partition support for Kafka spout > > > Key: EAGLE-42 > URL: https://issues.apache.org/jira/browse/EAGLE-42 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.3.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen >Priority: Minor > Fix For: v0.3.0 > > > This is not a issue any more. I will close this ticket -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-42) Customized partition support for Kafka spout
[ https://issues.apache.org/jira/browse/EAGLE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-42. -- Resolution: Not A Problem > Customized partition support for Kafka spout > > > Key: EAGLE-42 > URL: https://issues.apache.org/jira/browse/EAGLE-42 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.3.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen >Priority: Minor > Fix For: v0.3.0 > > > This is not a issue any more. I will close this ticket -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (EAGLE-42) Customized partition support for Kafka spout
[ https://issues.apache.org/jira/browse/EAGLE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen reopened EAGLE-42: add ticket description > Customized partition support for Kafka spout > > > Key: EAGLE-42 > URL: https://issues.apache.org/jira/browse/EAGLE-42 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.3.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen >Priority: Minor > Fix For: v0.3.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-98) Eagle Pipeline Scheduler
[
https://issues.apache.org/jira/browse/EAGLE-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen closed EAGLE-98.
--
Resolution: Not A Problem
> Eagle Pipeline Scheduler
>
>
> Key: EAGLE-98
> URL: https://issues.apache.org/jira/browse/EAGLE-98
> Project: Eagle
> Issue Type: Sub-task
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Zhao, Qingwen
>
> h2. Features
> * High Level Stream-Oriented
> * Declarative Streaming
> * Metadata Driven
> * Native Scala internal DSL
> * Support Scala Programing or Script/Configure in *.egl
> * Support static policy definition / dynamical policy loader
> * IDE friendly features like sql-prefix and xml as email template.
> * Name Reference
> h2. Syntax
> {code:language=scala}
> // Topology Definition API by extends or script
> import org.apache.eagle.stream.dsl.experimental.KafkaInterface._
> import org.apache.eagle.stream.dsl.experimental.DruidInterface._
> // #!/bin/bash
> // exec scala "$0" "$@"
> // !#
> // # start
> define ("metricStream_1") as ("name" -> 'string, "value"->'double,
> "timestamp"->'long) from
> kafka(topic="metricStream_1",zk=conf"kafka.zk.hosts",deserializer="")
> define ("metricStream_2") as ("name" -> 'string, "value"->'double,
> "timestamp"->'long) from
> kafka(topic="metricStream_2")
> define ("logStream_3") from kafka(topic="logStream_3")
> // filter by function
> filter ("logStream_3") by {(line,collector) => collector.collect(line)} as
> ("name" -> 'string, "value"->'double, "timestamp"->'long)
> // "logStream_3" as ("name" -> 'string, "value"->'double, "timestamp"->'long)
> // filter by pattern and rename stream
> filter("logStream_3"->"logStream_3_parsed") by
> """(?\d{4}-\d{2}-\d{2})""".r as ("name" -> 'string,
> "value"->'double, "timestamp"-> datetime("-MM-DD"))
> alert partitionBy "metricStream_1.metricType" parallism 1 by {sql"""
> from metricStream_1[component=='dn' and
> metricType=="RpcActivityForPort50020.RpcQueueTimeNumOps"].time[3600]
> select sum(value) group by host output every 1 hour insert into alertStream;
> """}
> aggregate partitionBy "metricStream_1.metricType" parallism 2 by {sql"""
> from metricStream_1[component=='dn' and
> metricType=="RpcActivityForPort50020.RpcQueueTimeNumOps"].time[3600]
> select sum(value) group by host output every 1 hour insert into
> aggregatedMetricStream_1;
> """}
> 'alertStream ~> kafka("alert_topic",zk=conf"kafka.zk.hosts")
> "alertStream" to mail(
> from = "sen...@eagle.incubator.apache.org",
> to = "recei...@eagle.incubator.apache.org",
> smtp = "localhost:25",
> template =
>
>
> Alert Notification
>
>
> Message
> $message
>
>
> )
> // split stream by logic
> 'aggregatedMetricStream_1 to kafka("aggregated_stream_dn") where "component
> == 'dn'" partitionBy "aggregatedMetricStream_1.metricType"
> 'aggregatedMetricStream_1 ~> druid("aggregated_stream_nn") where "component
> == 'nn'" partitionBy "aggregatedMetricStream_1.metricType"
> // # end
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (EAGLE-164) Tutorial for setting up the development environment on mac
[ https://issues.apache.org/jira/browse/EAGLE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen reopened EAGLE-164: - add ticket description > Tutorial for setting up the development environment on mac > -- > > Key: EAGLE-164 > URL: https://issues.apache.org/jira/browse/EAGLE-164 > Project: Eagle > Issue Type: Task >Affects Versions: v0.3.0 >Reporter: Su Ralph >Assignee: Zhao, Qingwen > Fix For: v0.3.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-164) Tutorial for setting up the development environment on mac
[ https://issues.apache.org/jira/browse/EAGLE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-164. --- Resolution: Done > Tutorial for setting up the development environment on mac > -- > > Key: EAGLE-164 > URL: https://issues.apache.org/jira/browse/EAGLE-164 > Project: Eagle > Issue Type: Task >Affects Versions: v0.3.0 >Reporter: Su Ralph >Assignee: Zhao, Qingwen > Fix For: v0.3.0 > > > Add a document on how to setup the development environment on Apple mac -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-164) Tutorial for setting up the development environment on mac
[ https://issues.apache.org/jira/browse/EAGLE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-164: Description: Add a document on how to setup the development environment on Apple mac > Tutorial for setting up the development environment on mac > -- > > Key: EAGLE-164 > URL: https://issues.apache.org/jira/browse/EAGLE-164 > Project: Eagle > Issue Type: Task >Affects Versions: v0.3.0 >Reporter: Su Ralph >Assignee: Zhao, Qingwen > Fix For: v0.3.0 > > > Add a document on how to setup the development environment on Apple mac -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-238) Support scheduling topology in local mode including start/stop/status operations
[ https://issues.apache.org/jira/browse/EAGLE-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-238. --- Resolution: Done > Support scheduling topology in local mode including start/stop/status > operations > > > Key: EAGLE-238 > URL: https://issues.apache.org/jira/browse/EAGLE-238 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.3.0 >Reporter: Hao Chen >Assignee: Zhao, Qingwen > Fix For: v0.4.0 > > > users can submit/stop a topology in the local mode, in which a topology runs > in a local thread -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (EAGLE-238) Support scheduling topology in local mode including start/stop/status operations
[ https://issues.apache.org/jira/browse/EAGLE-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen reopened EAGLE-238: - add ticket description > Support scheduling topology in local mode including start/stop/status > operations > > > Key: EAGLE-238 > URL: https://issues.apache.org/jira/browse/EAGLE-238 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.3.0 >Reporter: Hao Chen >Assignee: Zhao, Qingwen > Fix For: v0.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-350) Running queue metrics monitoring
[
https://issues.apache.org/jira/browse/EAGLE-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-350:
Description:
Hadoop running queue monitoring aims to collect some queue related metrics.
Currently we only fetch data from the following three apis.
* CLUSTER_SCHEDULER_URL = "ws/v1/cluster/scheduler"
* CLUSTER_METRICS_URL = "ws/v1/cluster/metrics"
* CLUSTER_RUNNING_APPS_URL = "ws/v1/cluster/apps?state=RUNNING"
Query the parsed result
http://localhost:9098/eagle-service/rest/entities?query=RunningQueueService[@site="sandbox"]{*}=1000
http://localhost:9098/eagle-service/rest/entities?query=GenericMetricService[]{*}=hadoop.queue.usedcapacity=1000
> Running queue metrics monitoring
> -
>
> Key: EAGLE-350
> URL: https://issues.apache.org/jira/browse/EAGLE-350
> Project: Eagle
> Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> Hadoop running queue monitoring aims to collect some queue related metrics.
> Currently we only fetch data from the following three apis.
> * CLUSTER_SCHEDULER_URL = "ws/v1/cluster/scheduler"
> * CLUSTER_METRICS_URL = "ws/v1/cluster/metrics"
> * CLUSTER_RUNNING_APPS_URL = "ws/v1/cluster/apps?state=RUNNING"
> Query the parsed result
> http://localhost:9098/eagle-service/rest/entities?query=RunningQueueService[@site="sandbox"]{*}=1000
> http://localhost:9098/eagle-service/rest/entities?query=GenericMetricService[]{*}=hadoop.queue.usedcapacity=1000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (EAGLE-350) Running queue metrics monitoring
[ https://issues.apache.org/jira/browse/EAGLE-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen reopened EAGLE-350: - Add the ticket description > Running queue metrics monitoring > - > > Key: EAGLE-350 > URL: https://issues.apache.org/jira/browse/EAGLE-350 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-372) Change AlertNotificationEntity#fields type from String to List
[ https://issues.apache.org/jira/browse/EAGLE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-372. --- Resolution: Not A Problem This class have been removed. So this is a deprecated issue > Change AlertNotificationEntity#fields type from String to List > --- > > Key: EAGLE-372 > URL: https://issues.apache.org/jira/browse/EAGLE-372 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-404) Updating configuration format check at the front end
[ https://issues.apache.org/jira/browse/EAGLE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen resolved EAGLE-404. - Resolution: Fixed > Updating configuration format check at the front end > > > Key: EAGLE-404 > URL: https://issues.apache.org/jira/browse/EAGLE-404 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.4.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.4.0 > > > Since Eagle 0.4.0, we change the configuration format of applications from > json format to java properties. > For example: > key1=value1 > key2=value2 > ... > During the format checking, eagle allows key string consisting of letter, > digits, and dot. This does not work for some properties containing '-'. For > example, namenode host may be 'host1.domain-1' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (EAGLE-408) Eagle-JPM job name normalize
[ https://issues.apache.org/jira/browse/EAGLE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15557374#comment-15557374 ] Zhao, Qingwen edited comment on EAGLE-408 at 10/8/16 6:37 AM: -- Added jobDefId & jobExeId in the job definition for both running and historic jobs jobDefId: a job definition id regardless of the job execution, which is extracted from job configuration#eagle.job.name jobExeId: a job execution id, similar to jobId was (Author: qingwzhao): Added jobDefId & jobExeId in the job definition for both running and historic jobs jobDefId: a job definition id regardless of the job execution jobExeId: a job execution id, similar to jobId > Eagle-JPM job name normalize > > > Key: EAGLE-408 > URL: https://issues.apache.org/jira/browse/EAGLE-408 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: wujinhu >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > > In order to detect abnormal jobs and compare with the history of the same > job, the hadoop users need to add a configure entry to the job config(like > -Dealge.job.name="my job name") so that they can get the history information > of the job with the same job name. In eagle jpm, we need read this configure > entry from configuration, add to job entities and flush to hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-408) Eagle-JPM job name normalize
[ https://issues.apache.org/jira/browse/EAGLE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen resolved EAGLE-408. - Resolution: Done > Eagle-JPM job name normalize > > > Key: EAGLE-408 > URL: https://issues.apache.org/jira/browse/EAGLE-408 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: wujinhu >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > > In order to detect abnormal jobs and compare with the history of the same > job, the hadoop users need to add a configure entry to the job config(like > -Dealge.job.name="my job name") so that they can get the history information > of the job with the same job name. In eagle jpm, we need read this configure > entry from configuration, add to job entities and flush to hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-408) Eagle-JPM job name normalize
[ https://issues.apache.org/jira/browse/EAGLE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15557374#comment-15557374 ] Zhao, Qingwen commented on EAGLE-408: - Added jobDefId & jobExeId in the job definition for both running and historic jobs jobDefId: a job definition id regardless of the job execution jobExeId: a job execution id, similar to jobId > Eagle-JPM job name normalize > > > Key: EAGLE-408 > URL: https://issues.apache.org/jira/browse/EAGLE-408 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: wujinhu >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > > In order to detect abnormal jobs and compare with the history of the same > job, the hadoop users need to add a configure entry to the job config(like > -Dealge.job.name="my job name") so that they can get the history information > of the job with the same job name. In eagle jpm, we need read this configure > entry from configuration, add to job entities and flush to hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-514) Add two job count apis
[ https://issues.apache.org/jira/browse/EAGLE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen resolved EAGLE-514. - Resolution: Done > Add two job count apis > -- > > Key: EAGLE-514 > URL: https://issues.apache.org/jira/browse/EAGLE-514 > Project: Eagle > Issue Type: New Feature >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > *Running job counting in timeline* > Description: number of Running job (stacked by job type) snapshot during a > period of time > /rest/mrJobs/runningJobCounts?site=sampleSite=900=2016-08-22%2020:13:00=2016-08-30%2024:13:00 > *History job counting by duration* > Description: group the jobs by duration, duration distribution, stack by job > type (only for history) > /rest/mrJobs/jobCountsByDuration?site=sampleSite=0,900=2016-08-22%2020:13:00=2016-08-29%2024:13:00 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-538) Add Mapreduce task level apis
[ https://issues.apache.org/jira/browse/EAGLE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen resolved EAGLE-538. - Resolution: Done > Add Mapreduce task level apis > -- > > Key: EAGLE-538 > URL: https://issues.apache.org/jira/browse/EAGLE-538 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > *Running task count by duration* > http://localhost:9090/rest/mrTasks/taskCountsByDuration?jobId=job_1=apollo=0,30,60=3 > *Task distribution by counterName* > http://localhost:9090/rest/mrTasks/taskDistribution/HDFS_BYTES_READ?site=sanbox=job_1=MAP=0,1 > *History task count in minute* > http://localhost:9090/rest/mrTasks/historyTaskCount?site=sanbox=job_1=2016-09-12%2005:31:13=2016-09-12%2005:33:10 > *Task suggestion* > http://localhost:9090/rest/mrTasks/taskSuggestion?site=sanbox_id=job_1_id=job_2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-554) EagleServiceBaseClient cannot configure the basePath
[ https://issues.apache.org/jira/browse/EAGLE-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen resolved EAGLE-554. - Resolution: Fixed > EagleServiceBaseClient cannot configure the basePath > > > Key: EAGLE-554 > URL: https://issues.apache.org/jira/browse/EAGLE-554 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > > From Eagle 0.5, the base path of EagleServiceBase Client becomes /rest. > To be compatible with the old versions (/eagle-service/rest), Eagle should > enable the base path configurable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-592) Add a hdfs audit log parser which consumes message in Json format
Zhao, Qingwen created EAGLE-592:
---
Summary: Add a hdfs audit log parser which consumes message in
Json format
Key: EAGLE-592
URL: https://issues.apache.org/jira/browse/EAGLE-592
Project: Eagle
Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Zhao, Qingwen
Assignee: Zhao, Qingwen
Fix For: v0.5.0
For some log collector agents, like filebeat (5.0), the output is in json
format.
{"xx": "abc", "yy": "aabbcc", "message": "audit log"}
This ticket will create a class MessageJsonScheme which will extract 'message'
field from the message from Kafka
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-563) refactor Hadoop queue feeder using application framework
[ https://issues.apache.org/jira/browse/EAGLE-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-563: Summary: refactor Hadoop queue feeder using application framework (was: refactor Hadoop quieue feeder using application framework) > refactor Hadoop queue feeder using application framework > > > Key: EAGLE-563 > URL: https://issues.apache.org/jira/browse/EAGLE-563 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Michael Wu > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-561) JsonMappingException in Hadoop queue feeder
[ https://issues.apache.org/jira/browse/EAGLE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-561: Assignee: Michael Wu (was: Zhao, Qingwen) > JsonMappingException in Hadoop queue feeder > --- > > Key: EAGLE-561 > URL: https://issues.apache.org/jira/browse/EAGLE-561 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Michael Wu > Fix For: v0.5.0 > > > This exception is caused by a yarn rest api bug: > https://issues.apache.org/jira/browse/YARN-4785 > the "type" field for LeafQueueInfo in response of RM REST API has > inconsistent value type ( String and Array ) . While String type is expected -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-562) Add a new metric totalVirtualCores in Hadoop queue feeder
[ https://issues.apache.org/jira/browse/EAGLE-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-562: Assignee: Michael Wu (was: Zhao, Qingwen) > Add a new metric totalVirtualCores in Hadoop queue feeder > - > > Key: EAGLE-562 > URL: https://issues.apache.org/jira/browse/EAGLE-562 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Michael Wu > > Since Hadoop 2.7, there is a new metric 'totalVirtualCores' in RM cluster > metrics API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-545) hdfs/bhase/yarn health check
[ https://issues.apache.org/jira/browse/EAGLE-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-545: Description: The app aims to monitor those services with a master-slave structured topology, and provides metrics at the HOST level. Specifically, this app will support the following services healthy check * HDFS: namenode, datanode, journalnode * HBASE: hmaster, regionservers * YARN: resourcemanager, nodemanagers, historyserver More detailed requirements: 1. provides node level health diagnosis including the master nodes and slave nodes 2. provide several cluster-level metrics was: 1. provides node level health diagnosis including the master nodes and slave nodes 2. provide several cluster-level metrics > hdfs/bhase/yarn health check > - > > Key: EAGLE-545 > URL: https://issues.apache.org/jira/browse/EAGLE-545 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > The app aims to monitor those services with a master-slave structured > topology, and provides metrics at the HOST level. Specifically, this app will > support the following services healthy check > * HDFS: namenode, datanode, journalnode > * HBASE: hmaster, regionservers > * YARN: resourcemanager, nodemanagers, historyserver > More detailed requirements: > 1. provides node level health diagnosis including the master nodes and slave > nodes > 2. provide several cluster-level metrics -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-563) refactor Hadoop quieue feeder using application framework
Zhao, Qingwen created EAGLE-563: --- Summary: refactor Hadoop quieue feeder using application framework Key: EAGLE-563 URL: https://issues.apache.org/jira/browse/EAGLE-563 Project: Eagle Issue Type: Improvement Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-562) Add a new metric totalVirtualCores in Hadoop queue feeder
Zhao, Qingwen created EAGLE-562: --- Summary: Add a new metric totalVirtualCores in Hadoop queue feeder Key: EAGLE-562 URL: https://issues.apache.org/jira/browse/EAGLE-562 Project: Eagle Issue Type: Improvement Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Since Hadoop 2.7, there is a new metric 'totalVirtualCores' in RM cluster metrics API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-561) JsonMappingException in Hadoop queue feeder
Zhao, Qingwen created EAGLE-561: --- Summary: JsonMappingException in Hadoop queue feeder Key: EAGLE-561 URL: https://issues.apache.org/jira/browse/EAGLE-561 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Fix For: v0.5.0 This exception is caused by a yarn rest api bug: https://issues.apache.org/jira/browse/YARN-4785 the "type" field for LeafQueueInfo in response of RM REST API has inconsistent value type ( String and Array ) . While String type is expected -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-554) EagleServiceBaseClient cannot configure the basePath
Zhao, Qingwen created EAGLE-554: --- Summary: EagleServiceBaseClient cannot configure the basePath Key: EAGLE-554 URL: https://issues.apache.org/jira/browse/EAGLE-554 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Fix For: v0.5.0 >From Eagle 0.5, the base path of EagleServiceBase Client becomes /rest. To be compatible with the old versions (/eagle-service/rest), Eagle should enable the base path configurable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-545) hdfs/bhase/yarn health check
Zhao, Qingwen created EAGLE-545: --- Summary: hdfs/bhase/yarn health check Key: EAGLE-545 URL: https://issues.apache.org/jira/browse/EAGLE-545 Project: Eagle Issue Type: New Feature Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen 1. provides node level health diagnosis including the master nodes and slave nodes 2. provide several cluster-level metrics -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-538) Add Mapreduce task level apis
[ https://issues.apache.org/jira/browse/EAGLE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-538: Description: *Running task count by duration* http://localhost:9090/rest/mrTasks/taskCountsByDuration?jobId=job_1=apollo=0,30,60=3 *Task distribution by counterName* http://localhost:9090/rest/mrTasks/taskDistribution/HDFS_BYTES_READ?site=sanbox=job_1=MAP=0,1 *History task count in minute* http://localhost:9090/rest/mrTasks/historyTaskCount?site=sanbox=job_1=2016-09-12%2005:31:13=2016-09-12%2005:33:10 *Task suggestion* http://localhost:9090/rest/mrTasks/taskSuggestion?site=sanbox_id=job_1_id=job_2 was: *Running task count by duration* http://localhost:9090/rest/mrTasks/taskCountsByDuration?jobId=job_1472330732014_12129=apollo=0,30,60=3 *Task distribution by counterName* http://localhost:9090/rest/mrTasks/taskDistribution/HDFS_BYTES_READ?site=apollo=job_1473431794035_32476=MAP=0,1 *History task count in minute* http://localhost:9090/rest/mrTasks/historyTaskCount?site=apollo=job_1473431794035_33228=2016-09-12%2005:31:13=2016-09-12%2005:33:10 *Task suggestion* http://localhost:9090/rest/mrTasks/taskSuggestion?site=apollo_id=job_1472854673519_33040_id=job_1473431794035_33181 > Add Mapreduce task level apis > -- > > Key: EAGLE-538 > URL: https://issues.apache.org/jira/browse/EAGLE-538 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > *Running task count by duration* > http://localhost:9090/rest/mrTasks/taskCountsByDuration?jobId=job_1=apollo=0,30,60=3 > *Task distribution by counterName* > http://localhost:9090/rest/mrTasks/taskDistribution/HDFS_BYTES_READ?site=sanbox=job_1=MAP=0,1 > *History task count in minute* > http://localhost:9090/rest/mrTasks/historyTaskCount?site=sanbox=job_1=2016-09-12%2005:31:13=2016-09-12%2005:33:10 > *Task suggestion* > http://localhost:9090/rest/mrTasks/taskSuggestion?site=sanbox_id=job_1_id=job_2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-538) Add Mapreduce task level apis
Zhao, Qingwen created EAGLE-538: --- Summary: Add Mapreduce task level apis Key: EAGLE-538 URL: https://issues.apache.org/jira/browse/EAGLE-538 Project: Eagle Issue Type: New Feature Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen *Running task count by duration* http://localhost:9090/rest/mrTasks/taskCountsByDuration?jobId=job_1472330732014_12129=apollo=0,30,60=3 *Task distribution by counterName* http://localhost:9090/rest/mrTasks/taskDistribution/HDFS_BYTES_READ?site=apollo=job_1473431794035_32476=MAP=0,1 *History task count in minute* http://localhost:9090/rest/mrTasks/historyTaskCount?site=apollo=job_1473431794035_33228=2016-09-12%2005:31:13=2016-09-12%2005:33:10 *Task suggestion* http://localhost:9090/rest/mrTasks/taskSuggestion?site=apollo_id=job_1472854673519_33040_id=job_1473431794035_33181 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-514) Add two job count apis
[ https://issues.apache.org/jira/browse/EAGLE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-514: Description: *Running job counting in timeline* Description: number of Running job (stacked by job type) snapshot during a period of time /rest/mrJobs/runningJobCounts?site=sampleSite=900=2016-08-22%2020:13:00=2016-08-30%2024:13:00 *History job counting by duration* Description: group the jobs by duration, duration distribution, stack by job type (only for history) /rest/mrJobs/jobCountsByDuration?site=sampleSite=0,900=2016-08-22%2020:13:00=2016-08-29%2024:13:00 was: *Running job counting in timeline* /rest/mrJobs/runningJobCounts?site=sampleSite=900=2016-08-22%2020:13:00=2016-08-30%2024:13:00 *History job counting by duration* /rest/mrJobs/jobCountsByDuration?site=sampleSite=0,900=2016-08-22%2020:13:00=2016-08-29%2024:13:00 > Add two job count apis > -- > > Key: EAGLE-514 > URL: https://issues.apache.org/jira/browse/EAGLE-514 > Project: Eagle > Issue Type: New Feature >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > *Running job counting in timeline* > Description: number of Running job (stacked by job type) snapshot during a > period of time > /rest/mrJobs/runningJobCounts?site=sampleSite=900=2016-08-22%2020:13:00=2016-08-30%2024:13:00 > *History job counting by duration* > Description: group the jobs by duration, duration distribution, stack by job > type (only for history) > /rest/mrJobs/jobCountsByDuration?site=sampleSite=0,900=2016-08-22%2020:13:00=2016-08-29%2024:13:00 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-514) Add two job count apis
Zhao, Qingwen created EAGLE-514: --- Summary: Add two job count apis Key: EAGLE-514 URL: https://issues.apache.org/jira/browse/EAGLE-514 Project: Eagle Issue Type: New Feature Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen *Running job counting in timeline* /rest/mrJobs/runningJobCounts?site=sampleSite=900=2016-08-22%2020:13:00=2016-08-30%2024:13:00 *History job counting by duration* /rest/mrJobs/jobCountsByDuration?site=sampleSite=0,900=2016-08-22%2020:13:00=2016-08-29%2024:13:00 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-467) Add job query apis for both running & historic jobs
[
https://issues.apache.org/jira/browse/EAGLE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen closed EAGLE-467.
---
Resolution: Done
> Add job query apis for both running & historic jobs
>
>
> Key: EAGLE-467
> URL: https://issues.apache.org/jira/browse/EAGLE-467
> Project: Eagle
> Issue Type: New Feature
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> *Job search rest api*
> /rest/mrJobs/search?jobId=?=?
> /rest/mrJobs/search?jobDefId=?=?
> Description: search all jobs by jobId or jobDefId
> QueryParam: jobId/jobIdId & site
> Return: job list with both running/historic jobs with no duplicate ones
> *Job list api*
> /rest/mrJobs?query=%s[@site=?]{*}=10=2016-08-10%2006:25:51=2016-08-10%2008:25:51
> Description: show all jobs in a site
> QueryParam: site
> Return: job list with both running/historic jobs with no duplicate ones
> *Task count statistic api*
> /rest/mrJobs/job_1471420935844_0278/taskCounts?site=apollo=0,30,60=3
> Description: return running/finished tasks with the task count value and top
> longest task set in each time slot
> QueryParam: site & timeslot list (seconds)
> Return:
> The problem is current we store running jobs and historic jobs into different
> places, which presents an obstacle when we want to query all jobs regardless
> of the status.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (EAGLE-473) Query error if query string contains "[]"
[
https://issues.apache.org/jira/browse/EAGLE-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen resolved EAGLE-473.
-
Resolution: Fixed
Assignee: Zhao, Qingwen
> Query error if query string contains "[]"
> -
>
> Key: EAGLE-473
> URL: https://issues.apache.org/jira/browse/EAGLE-473
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> Query
> string:[7279137F3E23471BBB397E52FC94543A/ED1F4AD763A64097B640A7CBD54F4AD9]
> Promoted Listing Job 2016/08/15/(25/29)
> {code}
> success: false,
> exception: "java.lang.Exception: java.io.IOException:
> org.apache.eagle.storage.exception.QueryCompileException:
> java.lang.IllegalArgumentException: List query syntax is
> []{} Aggregate query syntax is
> []{}.{}
> org.apache.eagle.storage.operation.QueryStatement.execute(QueryStatement.java:43)
>
> org.apache.eagle.service.generic.GenericEntityServiceResource.search(GenericEntityServiceResource.java:443)
>
> org.apache.eagle.service.jpm.MRJobExecutionResource.searchJobsById(MRJobExecutionResource.java:149)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method.invoke(Method.java:498)
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
>
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>
> org.apache.eagle.service.jpm.MRJobExecutionResource.searchJobsById(MRJobExecutionResource.java:158)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method.invoke(Method.java:498)
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
>
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> ",
> obj: [ ]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-467) Add job query apis for both running & historic jobs
[
https://issues.apache.org/jira/browse/EAGLE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-467:
Description:
*Job search rest api*
/rest/mrJobs/search?jobId=?=?
/rest/mrJobs/search?jobDefId=?=?
Description: search all jobs by jobId or jobDefId
QueryParam: jobId/jobIdId & site
Return: job list with both running/historic jobs with no duplicate ones
*Job list api*
/rest/mrJobs?query=%s[@site=?]{*}=10=2016-08-10%2006:25:51=2016-08-10%2008:25:51
Description: show all jobs in a site
QueryParam: site
Return: job list with both running/historic jobs with no duplicate ones
*Task count statistic api*
/rest/mrJobs/job_1471420935844_0278/taskCounts?site=apollo=0,30,60=3
Description: return running/finished tasks with the task count value and top
longest task set in each time slot
QueryParam: site & timeslot list (seconds)
Return:
The problem is current we store running jobs and historic jobs into different
places, which presents an obstacle when we want to query all jobs regardless of
the status.
was:
Job search rest api:
/rest/mrJobs/search?jobId=?=?
QueryParam: jobId & site
Return:
job list api:
/rest/mrJobs?query=%s[@site=?]{*}=10=2016-08-10%2006:25:51=2016-08-10%2008:25:51
task count statistic api:
/rest/mrJobs/job_1471420935844_0278/taskCounts?site=apollo=0,30,60=3
The problem is current we store running jobs and historic jobs into different
places, which presents an obstacle when we want to query all jobs regardless of
the status.
> Add job query apis for both running & historic jobs
>
>
> Key: EAGLE-467
> URL: https://issues.apache.org/jira/browse/EAGLE-467
> Project: Eagle
> Issue Type: New Feature
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> *Job search rest api*
> /rest/mrJobs/search?jobId=?=?
> /rest/mrJobs/search?jobDefId=?=?
> Description: search all jobs by jobId or jobDefId
> QueryParam: jobId/jobIdId & site
> Return: job list with both running/historic jobs with no duplicate ones
> *Job list api*
> /rest/mrJobs?query=%s[@site=?]{*}=10=2016-08-10%2006:25:51=2016-08-10%2008:25:51
> Description: show all jobs in a site
> QueryParam: site
> Return: job list with both running/historic jobs with no duplicate ones
> *Task count statistic api*
> /rest/mrJobs/job_1471420935844_0278/taskCounts?site=apollo=0,30,60=3
> Description: return running/finished tasks with the task count value and top
> longest task set in each time slot
> QueryParam: site & timeslot list (seconds)
> Return:
> The problem is current we store running jobs and historic jobs into different
> places, which presents an obstacle when we want to query all jobs regardless
> of the status.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-467) Add job query apis for both running & historic jobs
[
https://issues.apache.org/jira/browse/EAGLE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen updated EAGLE-467:
Description:
Job search rest api:
/rest/mrJobs/search?jobId=?=?
QueryParam: jobId & site
Return:
job list api:
/rest/mrJobs?query=%s[@site=?]{*}=10=2016-08-10%2006:25:51=2016-08-10%2008:25:51
task count statistic api:
/rest/mrJobs/job_1471420935844_0278/taskCounts?site=apollo=0,30,60=3
The problem is current we store running jobs and historic jobs into different
places, which presents an obstacle when we want to query all jobs regardless of
the status.
was:
Job search rest api:
/rest/mrJobs/search?jobId=?=?
job list api:
/rest/mrJobs?query=%s[@site=?]{*}=10=2016-08-10%2006:25:51=2016-08-10%2008:25:51
The problem is current we store running jobs and historic jobs into different
places, which presents an obstacle when we want to query all jobs regardless of
the status.
> Add job query apis for both running & historic jobs
>
>
> Key: EAGLE-467
> URL: https://issues.apache.org/jira/browse/EAGLE-467
> Project: Eagle
> Issue Type: New Feature
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> Job search rest api:
> /rest/mrJobs/search?jobId=?=?
> QueryParam: jobId & site
> Return:
> job list api:
> /rest/mrJobs?query=%s[@site=?]{*}=10=2016-08-10%2006:25:51=2016-08-10%2008:25:51
> task count statistic api:
> /rest/mrJobs/job_1471420935844_0278/taskCounts?site=apollo=0,30,60=3
> The problem is current we store running jobs and historic jobs into different
> places, which presents an obstacle when we want to query all jobs regardless
> of the status.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (EAGLE-473) Query error if query string contains "[]"
Zhao, Qingwen created EAGLE-473:
---
Summary: Query error if query string contains "[]"
Key: EAGLE-473
URL: https://issues.apache.org/jira/browse/EAGLE-473
Project: Eagle
Issue Type: Bug
Affects Versions: v0.3.0
Reporter: Zhao, Qingwen
Fix For: v0.5.0
Query
string:[7279137F3E23471BBB397E52FC94543A/ED1F4AD763A64097B640A7CBD54F4AD9]
Promoted Listing Job 2016/08/15/(25/29)
{code}
success: false,
exception: "java.lang.Exception: java.io.IOException:
org.apache.eagle.storage.exception.QueryCompileException:
java.lang.IllegalArgumentException: List query syntax is
[]{} Aggregate query syntax is
[]{}.{}
org.apache.eagle.storage.operation.QueryStatement.execute(QueryStatement.java:43)
org.apache.eagle.service.generic.GenericEntityServiceResource.search(GenericEntityServiceResource.java:443)
org.apache.eagle.service.jpm.MRJobExecutionResource.searchJobsById(MRJobExecutionResource.java:149)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:498)
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
org.apache.eagle.service.jpm.MRJobExecutionResource.searchJobsById(MRJobExecutionResource.java:158)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:498)
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
",
obj: [ ]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (EAGLE-467) Add job query apis for both running & historic jobs
Zhao, Qingwen created EAGLE-467:
---
Summary: Add job query apis for both running & historic jobs
Key: EAGLE-467
URL: https://issues.apache.org/jira/browse/EAGLE-467
Project: Eagle
Issue Type: New Feature
Reporter: Zhao, Qingwen
Assignee: Zhao, Qingwen
Job search rest api:
/rest/mrJobs/search?jobId=?=?
job list api:
/rest/mrJobs?query=%s[@site=?]{*}=10=2016-08-10%2006:25:51=2016-08-10%2008:25:51
The problem is current we store running jobs and historic jobs into different
places, which presents an obstacle when we want to query all jobs regardless of
the status.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (EAGLE-466) TestSerDeserPer failed with Windows Git bash
[
https://issues.apache.org/jira/browse/EAGLE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao, Qingwen resolved EAGLE-466.
-
Resolution: Fixed
> TestSerDeserPer failed with Windows Git bash
>
>
> Key: EAGLE-466
> URL: https://issues.apache.org/jira/browse/EAGLE-466
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
> Fix For: v0.5.0
>
>
> {code}
> java.io.FileNotFoundException: \tmp\file2.bin (The system cannot find the
> path specified)
> at java.io.FileOutputStream.open0(Native Method)
> at java.io.FileOutputStream.open(FileOutputStream.java:270)
> at java.io.FileOutputStream.(FileOutputStream.java:213)
> at java.io.FileOutputStream.(FileOutputStream.java:101)
> at
> org.apache.eagle.alert.engine.perf.TestSerDeserPer.testSerDeserPerf2(TestSerDeserPer.java:91)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:117)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:253)
> at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:84)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (EAGLE-466) TestSerDeserPer failed with Windows Git bash
Zhao, Qingwen created EAGLE-466:
---
Summary: TestSerDeserPer failed with Windows Git bash
Key: EAGLE-466
URL: https://issues.apache.org/jira/browse/EAGLE-466
Project: Eagle
Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Zhao, Qingwen
Assignee: Zhao, Qingwen
Fix For: v0.5.0
{code}
java.io.FileNotFoundException: \tmp\file2.bin (The system cannot find the path
specified)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(FileOutputStream.java:270)
at java.io.FileOutputStream.(FileOutputStream.java:213)
at java.io.FileOutputStream.(FileOutputStream.java:101)
at
org.apache.eagle.alert.engine.perf.TestSerDeserPer.testSerDeserPerf2(TestSerDeserPer.java:91)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:117)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:253)
at
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-427) Query startTime & endTime should support timestamp
[ https://issues.apache.org/jira/browse/EAGLE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-427: Summary: Query startTime & endTime should support timestamp (was: Query startTime & endTime should support long ) > Query startTime & endTime should support timestamp > --- > > Key: EAGLE-427 > URL: https://issues.apache.org/jira/browse/EAGLE-427 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > For TimeSeries metrics/entities query, users are required to provide the > startTime string and endTime string with the format "-mm-dd hh:MM:ss" > e.g. startTime=2016-07-25 06:00:00=2017-08-25 23:59:59 > Eagle should support long timestamp. For example: > startTime=12423223232343 & endTime=12322435439888 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-427) Query startTime & endTime should support long
Zhao, Qingwen created EAGLE-427: --- Summary: Query startTime & endTime should support long Key: EAGLE-427 URL: https://issues.apache.org/jira/browse/EAGLE-427 Project: Eagle Issue Type: Improvement Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen For TimeSeries metrics/entities query, users are required to provide the startTime string and endTime string with the format "-mm-dd hh:MM:ss" e.g. startTime=2016-07-25 06:00:00=2017-08-25 23:59:59 Eagle should support long timestamp. For example: startTime=12423223232343 & endTime=12322435439888 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-404) Updating configuration format check at the front end
Zhao, Qingwen created EAGLE-404: --- Summary: Updating configuration format check at the front end Key: EAGLE-404 URL: https://issues.apache.org/jira/browse/EAGLE-404 Project: Eagle Issue Type: Bug Affects Versions: v0.4.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen Fix For: v0.4.0 Since Eagle 0.4.0, we change the configuration format of applications from json format to java properties. For example: key1=value1 key2=value2 ... During the format checking, eagle allows key string consisting of letter, digits, and dot. This does not work for some properties containing '-'. For example, namenode host may be 'host1.domain-1' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-372) Change AlertNotificationEntity#fields type from String to List
[ https://issues.apache.org/jira/browse/EAGLE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen updated EAGLE-372: Affects Version/s: v0.5.0 Fix Version/s: v0.5.0 > Change AlertNotificationEntity#fields type from String to List > --- > > Key: EAGLE-372 > URL: https://issues.apache.org/jira/browse/EAGLE-372 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-349) Add batch processing apis for metadata in the new alert engine
[ https://issues.apache.org/jira/browse/EAGLE-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-349. --- Resolution: Done > Add batch processing apis for metadata in the new alert engine > -- > > Key: EAGLE-349 > URL: https://issues.apache.org/jira/browse/EAGLE-349 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > > Currently, Eagle can only add entities one by one in the new alert engine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-350) Running queue metrics monitoring
[ https://issues.apache.org/jira/browse/EAGLE-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-350. --- Resolution: Done > Running queue metrics monitoring > - > > Key: EAGLE-350 > URL: https://issues.apache.org/jira/browse/EAGLE-350 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
