[jira] [Created] (EAGLE-842) mr running job count in zookeeper does not match the number in hbase

[wujinhu (JIRA)]

wujinhu created EAGLE-842:
-

 Summary: mr running job count in zookeeper does not match the 
number in hbase
 Key: EAGLE-842
 URL: https://issues.apache.org/jira/browse/EAGLE-842
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: Lingang Deng
 Fix For: v0.5.0


As you know, we save running job basic information in zookeeper and will be 
moved when the job finished. However, as time goes on, some running job basic 
information still exists in zookeeper, and when you run the zookeeper command 
get /apps/mr/running/sandbox in zk shell, the number increases slowly. You can 
compare this with the RUNNING number in JPM Web widget.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-841) CorrelationSpout reads kafkaBrokerZkQuorum from datasource first

[wujinhu (JIRA)]

wujinhu created EAGLE-841:
-

 Summary: CorrelationSpout reads kafkaBrokerZkQuorum from 
datasource first
 Key: EAGLE-841
 URL: https://issues.apache.org/jira/browse/EAGLE-841
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


CorrelationSpout reads kafkaBrokerZkQuorum from datasource first



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-840) Task Failing Nodes List and bad node detection

[wujinhu (JIRA)]

wujinhu created EAGLE-840:
-

 Summary: Task Failing Nodes List and bad node detection
 Key: EAGLE-840
 URL: https://issues.apache.org/jira/browse/EAGLE-840
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


add Task Failing Nodes List and bad node detection



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-839) add job diagnostics

[wujinhu (JIRA)]

wujinhu created EAGLE-839:
-

 Summary: add job diagnostics
 Key: EAGLE-839
 URL: https://issues.apache.org/jira/browse/EAGLE-839
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


When job failed, get job diagnostics from JobUnsuccessfulCompletion event.
But the diagnostics from JobUnsuccessfulCompletion is simple, we format it by 
using task attempt error



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-835) Job failure diagnostics and Bad node detection

[wujinhu (JIRA)]

wujinhu created EAGLE-835:
-

 Summary: Job failure diagnostics and Bad node detection
 Key: EAGLE-835
 URL: https://issues.apache.org/jira/browse/EAGLE-835
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


1. Job failure diagnostics (task failure category)
2. Task Failing Nodes List and bad node detection
Based on pre-aggregated the same as job failure diagnostics



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-827) Coordinator schedule time out

[wujinhu (JIRA)]

wujinhu created EAGLE-827:
-

 Summary: Coordinator schedule time out
 Key: EAGLE-827
 URL: https://issues.apache.org/jira/browse/EAGLE-827
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: Garrett Li
 Fix For: v0.5.0


Coordinator schedule time out(fail to get exclusive lock) because of last fail



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-826) Coordinator throws NullPointerException when generateSpoutMonitorMetadata

[wujinhu (JIRA)]

wujinhu created EAGLE-826:
-

 Summary: Coordinator throws NullPointerException when 
generateSpoutMonitorMetadata
 Key: EAGLE-826
 URL: https://issues.apache.org/jira/browse/EAGLE-826
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: Garrett Li
 Fix For: v0.5.0


Coordinator throws NullPointerException when generateSpoutMonitorMetadata 
because data source is empty, should catch this exception



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-821) coordinator bug in alert engine

[wujinhu (JIRA)]

wujinhu created EAGLE-821:
-

 Summary: coordinator bug in alert engine
 Key: EAGLE-821
 URL: https://issues.apache.org/jira/browse/EAGLE-821
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: Zhao, Qingwen
 Fix For: v0.5.0


Coordinator has bugs below:
1. When I disable a policy, coordinator does not clear allocated queue
2. Coordinator can not schedule policies while there are alert bolts with no 
resources
3. When I create some policies with stream A and B, coordinator can not 
schedule policy with stream C although there are free resources
How to reproduce:
Create 8 or more policies with stream A and some policies with Stream B, then 
create policy with steam C, will reproduce 2 and 3(the number may depends). 
When you see all the alert bolts contains stream A, then disable policy with 
stream A, it will reproduce 1 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-817) add KillOptions when stop a topology

[wujinhu (JIRA)]

wujinhu created EAGLE-817:
-

 Summary: add KillOptions when stop a topology
 Key: EAGLE-817
 URL: https://issues.apache.org/jira/browse/EAGLE-817
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


add KillOptions when stop a topology avoid waiting killed topology disappear 
from storm cluster



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-814) fix alertId is null in AlertStreamEvent bug

[wujinhu (JIRA)]

wujinhu created EAGLE-814:
-

 Summary: fix alertId is null in AlertStreamEvent bug
 Key: EAGLE-814
 URL: https://issues.apache.org/jira/browse/EAGLE-814
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


alertId is null when call notifyAlert()
2016-11-29 02:42:34 Thread-18-alertPublishBolt 
org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl [ERROR] Fail 
invoking publisher's onAlert, continue
java.lang.IllegalArgumentException: data may not be null
at 
org.apache.commons.httpclient.util.EncodingUtil.getBytes(EncodingUtil.java:203) 
~[stormjar.jar:na]
at org.apache.commons.httpclient.util.URIUtil.encode(URIUtil.java:502) 
~[stormjar.jar:na]
at 
org.apache.commons.httpclient.util.URIUtil.encodeQuery(URIUtil.java:468) 
~[stormjar.jar:na]
at 
org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.buildAlertContext(AlertEmailGenerator.java:130)
 ~[stormjar.jar:na]
at 
org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:64)
 ~[stormjar.jar:na]
at 
org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:55)
 ~[stormjar.jar:na]
at 
org.apache.eagle.alert.engine.publisher.impl.AlertEmailPublisher.onAlert(AlertEmailPublisher.java:84)
 ~[stormjar.jar:na]
at 
org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:87)
 [stormjar.jar:na]
at 
org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.nextEvent(AlertPublisherImpl.java:70)
 [stormjar.jar:na]
at 
org.apache.eagle.alert.engine.runner.AlertPublisherBolt.execute(AlertPublisherBolt.java:84)
 [stormjar.jar:na]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-787) add healthy check for hadoop-queue/topology-health/spark-history apps

[wujinhu (JIRA)]

wujinhu created EAGLE-787:
-

 Summary: add healthy check for 
hadoop-queue/topology-health/spark-history apps
 Key: EAGLE-787
 URL: https://issues.apache.org/jira/browse/EAGLE-787
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


add healthy check for hadoop-queue/topology-health/spark-history apps



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-779) add a managed task to regularly schedule registered healthchecks

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-779.
-
Resolution: Resolved

> add a managed task to regularly schedule registered healthchecks
> 
>
> Key: EAGLE-779
> URL: https://issues.apache.org/jira/browse/EAGLE-779
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> add a managed task to regularly schedule registered healthchecks



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-779) add a managed task to regularly schedule registered healthchecks

[wujinhu (JIRA)]

wujinhu created EAGLE-779:
-

 Summary: add a managed task to regularly schedule registered 
healthchecks
 Key: EAGLE-779
 URL: https://issues.apache.org/jira/browse/EAGLE-779
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


add a managed task to regularly schedule registered healthchecks



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-772) simply refactor mr running job feeder

[wujinhu (JIRA)]

wujinhu created EAGLE-772:
-

 Summary: simply refactor mr running job feeder
 Key: EAGLE-772
 URL: https://issues.apache.org/jira/browse/EAGLE-772
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


Currently, both MRRunningJobFetchSpout and MRRunningJobParseBolt  try to delete 
application from zookeeper, the two threads probably delete the same 
applications.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-770) remove InterProcessMutex from JobHistoryZKStateManager

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-770.
-
Resolution: Fixed

> remove InterProcessMutex from JobHistoryZKStateManager
> --
>
> Key: EAGLE-770
> URL: https://issues.apache.org/jira/browse/EAGLE-770
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> InterProcessMutex works across JVMs. But our applications are running in 
> storm cluster, a storm worker may contains many task threads. So that the 
> lock is useless.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-770) remove InterProcessMutex from JobHistoryZKStateManager

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-770:
--
Summary: remove InterProcessMutex from JobHistoryZKStateManager  (was: 
remove InterProcessMutex from JobHistoryZKStateManager)

> remove InterProcessMutex from JobHistoryZKStateManager
> --
>
> Key: EAGLE-770
> URL: https://issues.apache.org/jira/browse/EAGLE-770
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> InterProcessMutex works across JVMs. But our applications are running in 
> storm cluster, a storm worker may contains many task threads. So that the 
> lock is useless.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-770) remove InterProcessMutex from JobHistoryZKStateManager

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-770:
--
Summary: remove InterProcessMutex from 
JobHistoryZKStateManager  (was: remove InterProcessMutex from 
JobHistoryZKStateManager)

> remove InterProcessMutex from JobHistoryZKStateManager
> 
>
> Key: EAGLE-770
> URL: https://issues.apache.org/jira/browse/EAGLE-770
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> InterProcessMutex works across JVMs. But our applications are running in 
> storm cluster, a storm worker may contains many task threads. So that the 
> lock is useless.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-770) remove InterProcessMutex from JobHistoryZKStateManager

[wujinhu (JIRA)]

wujinhu created EAGLE-770:
-

 Summary: remove InterProcessMutex from JobHistoryZKStateManager
 Key: EAGLE-770
 URL: https://issues.apache.org/jira/browse/EAGLE-770
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


InterProcessMutex works across JVMs. But our applications are running in storm 
cluster, a storm worker may contains many task threads. So that the lock is 
useless.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-764) MR history feeder support Health Checks

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-764.
-
Resolution: Fixed

> MR history feeder support Health Checks
> ---
>
> Key: EAGLE-764
> URL: https://issues.apache.org/jira/browse/EAGLE-764
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> MR history feeder support Health Checks
> Use Application Health Checks with DropWizard



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-764) MR history feeder support Health Checks

[wujinhu (JIRA)]

wujinhu created EAGLE-764:
-

 Summary: MR history feeder support Health Checks
 Key: EAGLE-764
 URL: https://issues.apache.org/jira/browse/EAGLE-764
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


MR history feeder support Health Checks
Use Application Health Checks with DropWizard



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-757) fix alert JdbcDatabaseHandler connection issue

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-757.
-
Resolution: Fixed

> fix alert JdbcDatabaseHandler connection issue
> --
>
> Key: EAGLE-757
> URL: https://issues.apache.org/jira/browse/EAGLE-757
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> 1. fix JdbcDatabaseHandler connection, could not share one connection
> 2. remove code like e.printStackTrace(); use log instead



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-742) check applications when remove site

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-742.
-
Resolution: Fixed

> check applications when remove site
> ---
>
> Key: EAGLE-742
> URL: https://issues.apache.org/jira/browse/EAGLE-742
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> When we want to remove site through rest api(below two), we need to check 
> applications. If applications number is not zero, then remove failed.
> Web ui should check success whether it is false or true
> @DELETE
> @Path("/{siteId}")
> @Produces(MediaType.APPLICATION_JSON)
> public RESTResponse deleteSiteBySiteId(@PathParam("siteId") 
> String siteId){
> }
> @DELETE
> @Consumes(MediaType.APPLICATION_JSON)
> @Produces(MediaType.APPLICATION_JSON)
> public RESTResponse deleteSiteByUUID(UUIDRequest uuidRequest){
> }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-757) fix alert JdbcDatabaseHandler connection issue

[wujinhu (JIRA)]

wujinhu created EAGLE-757:
-

 Summary: fix alert JdbcDatabaseHandler connection issue
 Key: EAGLE-757
 URL: https://issues.apache.org/jira/browse/EAGLE-757
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


1. fix JdbcDatabaseHandler connection, could not share one connection
2. remove code like e.printStackTrace(); use log instead



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-745) web ui should check success(true or false) when delete site

[wujinhu (JIRA)]

wujinhu created EAGLE-745:
-

 Summary: web ui should check success(true or false) when delete 
site
 Key: EAGLE-745
 URL: https://issues.apache.org/jira/browse/EAGLE-745
 Project: Eagle
  Issue Type: Sub-task
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: Jilin, Jiang
 Fix For: v0.5.0


web ui should check success(true or false) when delete site



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-742) check applications when remove site

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-742:
--
Description: 
When we want to remove site through rest api(below two), we need to check 
applications. If applications number is not zero, then remove failed.
Web ui should check success whether it is false or true

@DELETE
@Path("/{siteId}")
@Produces(MediaType.APPLICATION_JSON)
public RESTResponse deleteSiteBySiteId(@PathParam("siteId") String 
siteId){
}

@DELETE
@Consumes(MediaType.APPLICATION_JSON)
@Produces(MediaType.APPLICATION_JSON)
public RESTResponse deleteSiteByUUID(UUIDRequest uuidRequest){
}

  was:When we want to remove site, we need to check applications. If 
applications number is not zero, then remove failed.


> check applications when remove site
> ---
>
> Key: EAGLE-742
> URL: https://issues.apache.org/jira/browse/EAGLE-742
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> When we want to remove site through rest api(below two), we need to check 
> applications. If applications number is not zero, then remove failed.
> Web ui should check success whether it is false or true
> @DELETE
> @Path("/{siteId}")
> @Produces(MediaType.APPLICATION_JSON)
> public RESTResponse deleteSiteBySiteId(@PathParam("siteId") 
> String siteId){
> }
> @DELETE
> @Consumes(MediaType.APPLICATION_JSON)
> @Produces(MediaType.APPLICATION_JSON)
> public RESTResponse deleteSiteByUUID(UUIDRequest uuidRequest){
> }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-742) check applications when remove site

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-742:
--
Description: When we want to remove site, we need to check applications. If 
applications number is not zero, then remove failed.  (was: When site has been 
removed, streams defined are still there. We need remove them.)

> check applications when remove site
> ---
>
> Key: EAGLE-742
> URL: https://issues.apache.org/jira/browse/EAGLE-742
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> When we want to remove site, we need to check applications. If applications 
> number is not zero, then remove failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-742) check applications when remove site

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-742:
--
Summary: check applications when remove site  (was: disable streams when 
site has been removed)

> check applications when remove site
> ---
>
> Key: EAGLE-742
> URL: https://issues.apache.org/jira/browse/EAGLE-742
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> When site has been removed, streams defined are still there. We need remove 
> them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-742) disable streams when site has been removed

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-742:
--
Summary: disable streams when site has been removed  (was: delete streams 
when site has been removed)

> disable streams when site has been removed
> --
>
> Key: EAGLE-742
> URL: https://issues.apache.org/jira/browse/EAGLE-742
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> When site has been removed, streams defined are still there. We need remove 
> them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-742) delete streams when site has been removed

[wujinhu (JIRA)]

wujinhu created EAGLE-742:
-

 Summary: delete streams when site has been removed
 Key: EAGLE-742
 URL: https://issues.apache.org/jira/browse/EAGLE-742
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


When site has been removed, streams defined are still there. We need remove 
them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-715) optimize some configurations for alert

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-715.
-
Resolution: Fixed

> optimize some configurations for alert
> --
>
> Key: EAGLE-715
> URL: https://issues.apache.org/jira/browse/EAGLE-715
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> optimize some configurations for alert



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-715) optimize some configurations for alert

[wujinhu (JIRA)]

wujinhu created EAGLE-715:
-

 Summary: optimize some configurations for alert
 Key: EAGLE-715
 URL: https://issues.apache.org/jira/browse/EAGLE-715
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


optimize some configurations for alert



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-705) streams is null when call /rest/apps/ api

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-705.
-
Resolution: Fixed

> streams is null when call /rest/apps/ api
> -
>
> Key: EAGLE-705
> URL: https://issues.apache.org/jira/browse/EAGLE-705
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> streams is null when call /rest/apps/ api



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-705) streams is null when call /rest/apps/ api

[wujinhu (JIRA)]

wujinhu created EAGLE-705:
-

 Summary: streams is null when call /rest/apps/ api
 Key: EAGLE-705
 URL: https://issues.apache.org/jira/browse/EAGLE-705
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


streams is null when call /rest/apps/ api



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-700) API /policies/{policyId} throws exception if policy does not exist

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-700.
-
Resolution: Fixed

> API /policies/{policyId} throws exception if policy does not exist
> --
>
> Key: EAGLE-700
> URL: https://issues.apache.org/jira/browse/EAGLE-700
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> API /policies/{policyId} throws exception if policy does not exist



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-700) API /policies/{policyId} throws exception if policy does not exist

[wujinhu (JIRA)]

wujinhu created EAGLE-700:
-

 Summary: API /policies/{policyId} throws exception if policy does 
not exist
 Key: EAGLE-700
 URL: https://issues.apache.org/jira/browse/EAGLE-700
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


API /policies/{policyId} throws exception if policy does not exist



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-694) alert engine could not reduce alert bolt number when parallelism of policy reduces

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-694.
-
Resolution: Fixed

> alert engine could not reduce alert bolt number when parallelism of policy 
> reduces
> --
>
> Key: EAGLE-694
> URL: https://issues.apache.org/jira/browse/EAGLE-694
> Project: Eagle
>  Issue Type: Bug
>Reporter: wujinhu
>Assignee: wujinhu
>
> alert engine could not reduce alert bolt number when parallelism of policy 
> reduces



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-694) alert engine could not reduce alert bolt number when parallelism of policy reduces

[wujinhu (JIRA)]

wujinhu created EAGLE-694:
-

 Summary: alert engine could not reduce alert bolt number when 
parallelism of policy reduces
 Key: EAGLE-694
 URL: https://issues.apache.org/jira/browse/EAGLE-694
 Project: Eagle
  Issue Type: Bug
Reporter: wujinhu
Assignee: wujinhu


alert engine could not reduce alert bolt number when parallelism of policy 
reduces



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-659) MR history feeder and Alert Engine integration

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-659.
-
Resolution: Resolved

> MR history feeder and Alert Engine integration
> --
>
> Key: EAGLE-659
> URL: https://issues.apache.org/jira/browse/EAGLE-659
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> When JPM finds fail jobs, it will send data to kafka which will read by alert 
> engine and generates alerts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-659) MR history feeder and Alert Engine integraton

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-659:
--
Summary: MR history feeder and Alert Engine integraton  (was: Eagle JPM 
send fail job alerts by Alert Engine)

> MR history feeder and Alert Engine integraton
> -
>
> Key: EAGLE-659
> URL: https://issues.apache.org/jira/browse/EAGLE-659
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> When JPM finds fail jobs, it will send data to kafka which will read by alert 
> engine and generates alerts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-659) MR history feeder and Alert Engine integration

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-659:
--
Summary: MR history feeder and Alert Engine integration  (was: MR history 
feeder and Alert Engine integraton)

> MR history feeder and Alert Engine integration
> --
>
> Key: EAGLE-659
> URL: https://issues.apache.org/jira/browse/EAGLE-659
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> When JPM finds fail jobs, it will send data to kafka which will read by alert 
> engine and generates alerts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-682) fix /policies/{policyId}/publishments bug

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-682.
-
Resolution: Fixed

> fix /policies/{policyId}/publishments bug
> -
>
> Key: EAGLE-682
> URL: https://issues.apache.org/jira/browse/EAGLE-682
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> fix null policy id exception



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-679) Fix missing CoprocessorService and MR Running feeder task number limitation

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-679.
-
Resolution: Fixed

> Fix missing CoprocessorService and MR Running feeder task number limitation
> ---
>
> Key: EAGLE-679
> URL: https://issues.apache.org/jira/browse/EAGLE-679
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> 1. fix missing CoprocessorService
> ERROR [2016-10-25 02:56:34,495] net.sf.extcos.internal.JavaResourceAccessor: 
> Unable to read interface 
> [org.apache.hadoop.hbase.coprocessor.CoprocessorService]
> ! java.io.IOException: Class not found
> 2. If task number of a job greater than 5000, then does not fetch task details



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-682) fix /policies/{policyId}/publishments bug

[wujinhu (JIRA)]

wujinhu created EAGLE-682:
-

 Summary: fix /policies/{policyId}/publishments bug
 Key: EAGLE-682
 URL: https://issues.apache.org/jira/browse/EAGLE-682
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


fix null policy id exception



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-679) Fix missing CoprocessorService and MR Running feeder task number limitation

[wujinhu (JIRA)]

wujinhu created EAGLE-679:
-

 Summary: Fix missing CoprocessorService and MR Running feeder task 
number limitation
 Key: EAGLE-679
 URL: https://issues.apache.org/jira/browse/EAGLE-679
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


1. fix missing CoprocessorService
ERROR [2016-10-25 02:56:34,495] net.sf.extcos.internal.JavaResourceAccessor: 
Unable to read interface 
[org.apache.hadoop.hbase.coprocessor.CoprocessorService]
! java.io.IOException: Class not found
2. If task number of a job greater than 5000, then does not fetch task details



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-674) fix grouping between AlertBolt and AlertPublisher

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-674.
-
Resolution: Fixed

> fix grouping between AlertBolt and AlertPublisher
> -
>
> Key: EAGLE-674
> URL: https://issues.apache.org/jira/browse/EAGLE-674
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> Currently, it is fields grouping
> boltDeclarer.fieldsGrouping(alertBoltNamePrefix + i, new 
> Fields(AlertConstants.FIELD_0));
> Sometimes, traffic will go to only one task of alert publisher, we should 
> change to shuffleGrouping



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-674) fix grouping between AlertBolt and AlertPublisher

[wujinhu (JIRA)]

wujinhu created EAGLE-674:
-

 Summary: fix grouping between AlertBolt and AlertPublisher
 Key: EAGLE-674
 URL: https://issues.apache.org/jira/browse/EAGLE-674
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


Currently, it is fields grouping
boltDeclarer.fieldsGrouping(alertBoltNamePrefix + i, new 
Fields(AlertConstants.FIELD_0));

Sometimes, traffic will go to only one task of alert publisher, we should 
change to shuffleGrouping



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-673) add numOfPublishBolts to alert engine topology

[wujinhu (JIRA)]

wujinhu created EAGLE-673:
-

 Summary: add numOfPublishBolts to alert engine topology
 Key: EAGLE-673
 URL: https://issues.apache.org/jira/browse/EAGLE-673
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


When creates alert engine topology
BoltDeclarer boltDeclarer = builder.setBolt(alertPublishBoltName, 
publisherBolt).setNumTasks(numOfPublishTasks);

builder does not set number of publish bolts which will cause these tasks are 
in only one bolt.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-146) SiddhiExtensionLoader Error: viewing zip file for jar:./lib/ojdbc6.jar

[wujinhu (JIRA)]

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

wujinhu commented on EAGLE-146:
---

I researched this issue and it was caused by storm installation.
In SiddhiExtensionLoader, it loads all jar files from class path and storm libs 
are also contained in class path
public static Map loadSiddhiExtensions() {
String classPath = System.getProperty(CLASS_PATH);
..
for (String element : classPathElements) {
extensionsList.addAll(getResources(element, pattern));
}
..
}
In storm lib directory, it contains ojdbc6.jar but it is just a link to another 
file which does not exists
[20:03]:[root@eagle006:~]# ls -lh /usr/share/java/ojdbc6.jar
ls: cannot access /usr/share/java/ojdbc6.jar: No such file or directory
So, that is the problem.


> SiddhiExtensionLoader Error: viewing zip file for jar:./lib/ojdbc6.jar
> --
>
> Key: EAGLE-146
> URL: https://issues.apache.org/jira/browse/EAGLE-146
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> {code}
> 2016-02-02 02:46:23 o.a.e.p.PolicyManager [INFO] Supported policy type : 
> siddhiCEPEngine
> 2016-02-02 02:46:23 o.a.e.p.PolicyManager [INFO] Supported policy type : 
> MachineLearning
> 2016-02-02 02:46:23 o.w.s.c.u.SiddhiExtensionLoader [ERROR] Error viewing zip 
> file for jar:./lib/ojdbc6.jar
> java.io.FileNotFoundException: ./lib/ojdbc6.jar (No such file or directory)
> at java.util.zip.ZipFile.open(Native Method) ~[na:1.7.0_60]
> at java.util.zip.ZipFile.(ZipFile.java:215) ~[na:1.7.0_60]
> at java.util.zip.ZipFile.(ZipFile.java:145) ~[na:1.7.0_60]
> at java.util.zip.ZipFile.(ZipFile.java:159) ~[na:1.7.0_60]
> at 
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContentFromJarFile(SiddhiExtensionLoader.java:111)
>  [stormjar.jar:na]
> at 
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContent(SiddhiExtensionLoader.java:82)
>  [stormjar.jar:na]
> at 
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContentFromDirectory(SiddhiExtensionLoader.java:101)
>  [stormjar.jar:na]
> at 
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContent(SiddhiExtensionLoader.java:77)
>  [stormjar.jar:na]
> at 
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContentFromDirectory(SiddhiExtensionLoader.java:101)
>  [stormjar.jar:na]
> at 
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getContent(SiddhiExtensionLoader.java:77)
>  [stormjar.jar:na]
> at 
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.getResources(SiddhiExtensionLoader.java:71)
>  [stormjar.jar:na]
> at 
> org.wso2.siddhi.core.util.SiddhiExtensionLoader.loadSiddhiExtensions(SiddhiExtensionLoader.java:51)
>  [stormjar.jar:na]
> at 
> org.wso2.siddhi.core.config.SiddhiContext.(SiddhiContext.java:35) 
> [stormjar.jar:na]
> at org.wso2.siddhi.core.SiddhiManager.(SiddhiManager.java:40) 
> [stormjar.jar:na]
> at 
> org.apache.eagle.policy.siddhi.SiddhiPolicyEvaluator.createSiddhiRuntime(SiddhiPolicyEvaluator.java:108)
>  [stormjar.jar:na]
> at 
> org.apache.eagle.policy.siddhi.SiddhiPolicyEvaluator.init(SiddhiPolicyEvaluator.java:83)
>  [stormjar.jar:na]
> at 
> org.apache.eagle.policy.siddhi.SiddhiPolicyEvaluator.(SiddhiPolicyEvaluator.java:79)
>  [stormjar.jar:na]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method) [na:1.7.0_60]
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>  [na:1.7.0_60]
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>  [na:1.7.0_60]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526) 
> [na:1.7.0_60]
> at 
> org.apache.eagle.policy.executor.PolicyProcessExecutor.createPolicyEvaluator(PolicyProcessExecutor.java:243)
>  [stormjar.jar:na]
> at 
> org.apache.eagle.policy.executor.PolicyProcessExecutor.init(PolicyProcessExecutor.java:188)
>  [stormjar.jar:na]
> at 
> org.apache.eagle.datastream.storm.JavaStormBoltWrapper.prepare(JavaStormBoltWrapper.scala:36)
>  [stormjar.jar:na]
> at 
> backtype.storm.daemon.executor$fn__5697$fn__5710.invoke(executor.clj:732) 
> [storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
> at backtype.storm.util$async_loop$fn__452.invoke(util.clj:463) 
> [storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
> at clojure.lang.AFn.run(AFn.java:24) [clojure-1.5.1.jar:na]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]
> 2016-02-02 02:46:23 

[jira] [Closed] (EAGLE-655) Fix metadata bug

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-655.
-
Resolution: Fixed

> Fix metadata bug
> 
>
> Key: EAGLE-655
> URL: https://issues.apache.org/jira/browse/EAGLE-655
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> fix metadata bug, context saved to metastore



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-653) remove zk root from configure

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-653.
-
Resolution: Resolved

> remove zk root from configure
> -
>
> Key: EAGLE-653
> URL: https://issues.apache.org/jira/browse/EAGLE-653
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> add applicationListener to MR feeders so that they can check some 
> environments like connection... before they start



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-653) remove zk root from configure

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-653:
--
Summary: remove zk root from configure  (was: Add ApplicationListener To MR 
Feeders)

> remove zk root from configure
> -
>
> Key: EAGLE-653
> URL: https://issues.apache.org/jira/browse/EAGLE-653
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> add applicationListener to MR feeders so that they can check some 
> environments like connection... before they start



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-653) Add ApplicationListener To MR Feeders

[wujinhu (JIRA)]

wujinhu created EAGLE-653:
-

 Summary: Add ApplicationListener To MR Feeders
 Key: EAGLE-653
 URL: https://issues.apache.org/jira/browse/EAGLE-653
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


add applicationListener to MR feeders so that they can check some environments 
like connection... before they start



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-644) optimize some default configurations for JPM

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-644.
-
Resolution: Resolved

> optimize some default configurations for JPM
> 
>
> Key: EAGLE-644
> URL: https://issues.apache.org/jira/browse/EAGLE-644
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> optimize some default configurations for JPM



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-644) optimize some default configurations for JPM

[wujinhu (JIRA)]

wujinhu created EAGLE-644:
-

 Summary: optimize some default configurations for JPM
 Key: EAGLE-644
 URL: https://issues.apache.org/jira/browse/EAGLE-644
 Project: Eagle
  Issue Type: Improvement
Reporter: wujinhu
Assignee: wujinhu


optimize some default configurations for JPM



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-642) move application runtime configure to ApplicationEntity context

[wujinhu (JIRA)]

wujinhu created EAGLE-642:
-

 Summary: move application runtime configure to ApplicationEntity 
context
 Key: EAGLE-642
 URL: https://issues.apache.org/jira/browse/EAGLE-642
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


When install an application, there are some configures like appId/siteId that 
should not changed by user, so we move them to context.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-43) Eagle Job Running Spout should support HTTPS

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-43.

   Resolution: Fixed
Fix Version/s: v0.5.0

> Eagle Job Running Spout should support HTTPS
> 
>
> Key: EAGLE-43
> URL: https://issues.apache.org/jira/browse/EAGLE-43
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Libin, Sun
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> Job Running Spout is a data source for hive security monitoring, it get data 
> from RM yarn API and RM web page, currently we only support HTTP, should add 
> HTTPS supprot



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-638) clean up configuration for Eagle JPM aggregation feeder

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-638.
-
Resolution: Resolved

> clean up configuration for Eagle JPM aggregation feeder
> ---
>
> Key: EAGLE-638
> URL: https://issues.apache.org/jira/browse/EAGLE-638
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> 1. remove useless configure
> 2. add required field to application provider.xml
> 3. add description to application provider.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-638) clean up configuration for Eagle JPM aggregation feeder

[wujinhu (JIRA)]

wujinhu created EAGLE-638:
-

 Summary: clean up configuration for Eagle JPM aggregation feeder
 Key: EAGLE-638
 URL: https://issues.apache.org/jira/browse/EAGLE-638
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


1. remove useless configure
2. add required field to application provider.xml
3. add description to application provider.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-558) Use dynamical loaded jarPath as default value in ApplicationEntity

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-558.
-
Resolution: Resolved

> Use dynamical loaded jarPath as default value in ApplicationEntity
> --
>
> Key: EAGLE-558
> URL: https://issues.apache.org/jira/browse/EAGLE-558
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> Use dynamical loaded jarPath as default value in ApplicationEntity, which 
> could also be forcefully replaced with InstallOperation
> It's an improvement from patch: 
> https://github.com/apache/incubator-eagle/commit/6fc103338fa3e3275a1357144dfab2feb1a103ec#diff-c9c5f683c463429e5e1c01b8b6fa71b7



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-634) clean up configuration for MR running feeder

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-634.
-
Resolution: Resolved

> clean up configuration for MR running feeder
> 
>
> Key: EAGLE-634
> URL: https://issues.apache.org/jira/browse/EAGLE-634
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> 1. remove useless configure
> 2. add required field to application provider.xml
> 3. add description to application provider.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-634) clean up configuration for MR running feeder

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-634:
--
Description: 
1. remove useless configure
2. add required field to application provider.xml
3. add description to application provider.xml

> clean up configuration for MR running feeder
> 
>
> Key: EAGLE-634
> URL: https://issues.apache.org/jira/browse/EAGLE-634
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> 1. remove useless configure
> 2. add required field to application provider.xml
> 3. add description to application provider.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-634) clean up configuration for MR running feeder

[wujinhu (JIRA)]

wujinhu created EAGLE-634:
-

 Summary: clean up configuration for MR running feeder
 Key: EAGLE-634
 URL: https://issues.apache.org/jira/browse/EAGLE-634
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-633) MR history feeder read some configurations from eagle server

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-633.
-
Resolution: Resolved

> MR history feeder read some configurations from eagle server
> 
>
> Key: EAGLE-633
> URL: https://issues.apache.org/jira/browse/EAGLE-633
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> application can read some configurations from eagle server like 
> service/zookeeper so that user does not need read from configure file



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-632) clean up configuration for MR history feeder

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-632.
-
Resolution: Resolved

> clean up configuration for MR history feeder
> 
>
> Key: EAGLE-632
> URL: https://issues.apache.org/jira/browse/EAGLE-632
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> 1. remove useless configure
> 2. add required field to application provider.xml
> 3. add description to application provider.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-633) MR history feeder read some configurations from eagle server

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-633:
--
Summary: MR history feeder read some configurations from eagle server  
(was: applications read some configurations from eagle server)

> MR history feeder read some configurations from eagle server
> 
>
> Key: EAGLE-633
> URL: https://issues.apache.org/jira/browse/EAGLE-633
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> application can read some configurations from eagle server like 
> service/zookeeper so that user does not need read from configure file



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-633) applications read some configurations from eagle server

[wujinhu (JIRA)]

wujinhu created EAGLE-633:
-

 Summary: applications read some configurations from eagle server
 Key: EAGLE-633
 URL: https://issues.apache.org/jira/browse/EAGLE-633
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


application can read some configurations from eagle server like 
service/zookeeper so that user does not need read from configure file



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-632) clean up configuration for MR history feeder

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-632:
--
Description: 
1. remove useless configure
2. add required field to application provider.xml
3. add description to application provider.xml

  was:
1. remove useless configure
2. add required field to application provider.xml


> clean up configuration for MR history feeder
> 
>
> Key: EAGLE-632
> URL: https://issues.apache.org/jira/browse/EAGLE-632
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> 1. remove useless configure
> 2. add required field to application provider.xml
> 3. add description to application provider.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-632) clean up configuration for MR feeders

[wujinhu (JIRA)]

wujinhu created EAGLE-632:
-

 Summary: clean up configuration for MR feeders
 Key: EAGLE-632
 URL: https://issues.apache.org/jira/browse/EAGLE-632
 Project: Eagle
  Issue Type: Improvement
Reporter: wujinhu
Assignee: wujinhu


1. remove useless configure
2. add required field to application provider.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-628) Fix jdbc metadata bugs

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-628.
-
Resolution: Fixed

> Fix jdbc metadata bugs
> --
>
> Key: EAGLE-628
> URL: https://issues.apache.org/jira/browse/EAGLE-628
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> 1. when Site Id/Display Name/Description is missing, it will fail to create 
> site(some flelds of sql are missing).
> 2. configuration should be saved in applicationentity
> 3. enable update application entity
> 4. fix application descriptor of applicationEntity: fetch from 
> ApplicationProviderService
> 5. delete site throw exception
> Caused by: java.sql.SQLException: Parameter index out of range (2 > number of 
> parameters, which is 1).
>   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:996)
>   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:935)
>   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:924)
>   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:870)
>   at 
> com.mysql.jdbc.PreparedStatement.checkBounds(PreparedStatement.java:3391)
>   at 
> com.mysql.jdbc.PreparedStatement.setInternal(PreparedStatement.java:3376)
>   at 
> com.mysql.jdbc.PreparedStatement.setString(PreparedStatement.java:4102)
>   at 
> org.apache.commons.dbcp.DelegatingPreparedStatement.setString(DelegatingPreparedStatement.java:135)
>   at 
> org.apache.commons.dbcp.DelegatingPreparedStatement.setString(DelegatingPreparedStatement.java:135)
>   at 
> org.apache.eagle.metadata.store.jdbc.service.orm.SiteEntityToRelation.accept(SiteEntityToRelation.java:56)
>   at 
> org.apache.eagle.metadata.store.jdbc.service.orm.SiteEntityToRelation.accept(SiteEntityToRelation.java:29)
>   at 
> org.apache.eagle.metadata.store.jdbc.JDBCMetadataMetadataStoreServiceImpl.update(JDBCMetadataMetadataStoreServiceImpl.java:216)
>   at org.apache.eagle.metadata.store.jdbc.service.SiteEnt



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-628) Fix jdbc metadata bugs

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-628:
--
Description: 
1. when Site Id/Display Name/Description is missing, it will fail to create 
site(some flelds of sql are missing).
2. configuration should be saved in applicationentity
3. enable update application entity
4. fix application descriptor of applicationEntity: fetch from 
ApplicationProviderService
5. delete site throw exception
Caused by: java.sql.SQLException: Parameter index out of range (2 > number of 
parameters, which is 1).
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:996)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:935)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:924)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:870)
at 
com.mysql.jdbc.PreparedStatement.checkBounds(PreparedStatement.java:3391)
at 
com.mysql.jdbc.PreparedStatement.setInternal(PreparedStatement.java:3376)
at 
com.mysql.jdbc.PreparedStatement.setString(PreparedStatement.java:4102)
at 
org.apache.commons.dbcp.DelegatingPreparedStatement.setString(DelegatingPreparedStatement.java:135)
at 
org.apache.commons.dbcp.DelegatingPreparedStatement.setString(DelegatingPreparedStatement.java:135)
at 
org.apache.eagle.metadata.store.jdbc.service.orm.SiteEntityToRelation.accept(SiteEntityToRelation.java:56)
at 
org.apache.eagle.metadata.store.jdbc.service.orm.SiteEntityToRelation.accept(SiteEntityToRelation.java:29)
at 
org.apache.eagle.metadata.store.jdbc.JDBCMetadataMetadataStoreServiceImpl.update(JDBCMetadataMetadataStoreServiceImpl.java:216)
at org.apache.eagle.metadata.store.jdbc.service.SiteEnt

  was:
1. when Site Id/Display Name/Description is missing, it will fail to create 
site(some flelds of sql are missing).
2. configuration should be saved in applicationentity
3. enable update application entity
4. throw IllegalArgumentException("Duplicated appId), but table is empty
5. delete site throw exception
Caused by: java.sql.SQLException: Parameter index out of range (2 > number of 
parameters, which is 1).
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:996)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:935)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:924)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:870)
at 
com.mysql.jdbc.PreparedStatement.checkBounds(PreparedStatement.java:3391)
at 
com.mysql.jdbc.PreparedStatement.setInternal(PreparedStatement.java:3376)
at 
com.mysql.jdbc.PreparedStatement.setString(PreparedStatement.java:4102)
at 
org.apache.commons.dbcp.DelegatingPreparedStatement.setString(DelegatingPreparedStatement.java:135)
at 
org.apache.commons.dbcp.DelegatingPreparedStatement.setString(DelegatingPreparedStatement.java:135)
at 
org.apache.eagle.metadata.store.jdbc.service.orm.SiteEntityToRelation.accept(SiteEntityToRelation.java:56)
at 
org.apache.eagle.metadata.store.jdbc.service.orm.SiteEntityToRelation.accept(SiteEntityToRelation.java:29)
at 
org.apache.eagle.metadata.store.jdbc.JDBCMetadataMetadataStoreServiceImpl.update(JDBCMetadataMetadataStoreServiceImpl.java:216)
at org.apache.eagle.metadata.store.jdbc.service.SiteEnt


> Fix jdbc metadata bugs
> --
>
> Key: EAGLE-628
> URL: https://issues.apache.org/jira/browse/EAGLE-628
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> 1. when Site Id/Display Name/Description is missing, it will fail to create 
> site(some flelds of sql are missing).
> 2. configuration should be saved in applicationentity
> 3. enable update application entity
> 4. fix application descriptor of applicationEntity: fetch from 
> ApplicationProviderService
> 5. delete site throw exception
> Caused by: java.sql.SQLException: Parameter index out of range (2 > number of 
> parameters, which is 1).
>   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:996)
>   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:935)
>   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:924)
>   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:870)
>   at 
> com.mysql.jdbc.PreparedStatement.checkBounds(PreparedStatement.java:3391)
>   at 
> com.mysql.jdbc.PreparedStatement.setInternal(PreparedStatement.java:3376)
>   at 
> com.mysql.jdbc.PreparedStatement.setString(PreparedStatement.java:4102)
>   at 
> org.apache.commons.dbcp.DelegatingPreparedStatement.setString(DelegatingPreparedStatement.java:135)
>   at 
> 

[jira] [Updated] (EAGLE-628) Fix jdbc metadata bugs

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-628:
--
Description: 
1. when Site Id/Display Name/Description is missing, it will fail to create 
site(some flelds of sql are missing).
2. configuration should be saved in applicationentity
3. enable update application entity
4. throw IllegalArgumentException("Duplicated appId), but table is empty
5. delete site throw exception
Caused by: java.sql.SQLException: Parameter index out of range (2 > number of 
parameters, which is 1).
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:996)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:935)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:924)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:870)
at 
com.mysql.jdbc.PreparedStatement.checkBounds(PreparedStatement.java:3391)
at 
com.mysql.jdbc.PreparedStatement.setInternal(PreparedStatement.java:3376)
at 
com.mysql.jdbc.PreparedStatement.setString(PreparedStatement.java:4102)
at 
org.apache.commons.dbcp.DelegatingPreparedStatement.setString(DelegatingPreparedStatement.java:135)
at 
org.apache.commons.dbcp.DelegatingPreparedStatement.setString(DelegatingPreparedStatement.java:135)
at 
org.apache.eagle.metadata.store.jdbc.service.orm.SiteEntityToRelation.accept(SiteEntityToRelation.java:56)
at 
org.apache.eagle.metadata.store.jdbc.service.orm.SiteEntityToRelation.accept(SiteEntityToRelation.java:29)
at 
org.apache.eagle.metadata.store.jdbc.JDBCMetadataMetadataStoreServiceImpl.update(JDBCMetadataMetadataStoreServiceImpl.java:216)
at org.apache.eagle.metadata.store.jdbc.service.SiteEnt

  was:
1. when Site Id/Display Name/Description is missing, it will fail to create 
site(some flelds of sql are missing).
2. configuration should be saved in applicationentity
3. enable update application entity
4. throw IllegalArgumentException("Duplicated appId), but table is empty


> Fix jdbc metadata bugs
> --
>
> Key: EAGLE-628
> URL: https://issues.apache.org/jira/browse/EAGLE-628
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> 1. when Site Id/Display Name/Description is missing, it will fail to create 
> site(some flelds of sql are missing).
> 2. configuration should be saved in applicationentity
> 3. enable update application entity
> 4. throw IllegalArgumentException("Duplicated appId), but table is empty
> 5. delete site throw exception
> Caused by: java.sql.SQLException: Parameter index out of range (2 > number of 
> parameters, which is 1).
>   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:996)
>   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:935)
>   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:924)
>   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:870)
>   at 
> com.mysql.jdbc.PreparedStatement.checkBounds(PreparedStatement.java:3391)
>   at 
> com.mysql.jdbc.PreparedStatement.setInternal(PreparedStatement.java:3376)
>   at 
> com.mysql.jdbc.PreparedStatement.setString(PreparedStatement.java:4102)
>   at 
> org.apache.commons.dbcp.DelegatingPreparedStatement.setString(DelegatingPreparedStatement.java:135)
>   at 
> org.apache.commons.dbcp.DelegatingPreparedStatement.setString(DelegatingPreparedStatement.java:135)
>   at 
> org.apache.eagle.metadata.store.jdbc.service.orm.SiteEntityToRelation.accept(SiteEntityToRelation.java:56)
>   at 
> org.apache.eagle.metadata.store.jdbc.service.orm.SiteEntityToRelation.accept(SiteEntityToRelation.java:29)
>   at 
> org.apache.eagle.metadata.store.jdbc.JDBCMetadataMetadataStoreServiceImpl.update(JDBCMetadataMetadataStoreServiceImpl.java:216)
>   at org.apache.eagle.metadata.store.jdbc.service.SiteEnt



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-628) Fix jdbc metadata bugs

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-628:
--
Description: 
1. when Site Id/Display Name/Description is missing, it will fail to create 
site(filed of sql is missing).
2. configuration should be saved in applicationentity
3. enable update application entity
4. throw IllegalArgumentException("Duplicated appId), but table is empty

  was:
1. When Site Id/Display Name/Description is missing, it will fail to create 
site(filed of sql is missing).
2. configuration should be saved in applicationentity
3. enable update application entity


> Fix jdbc metadata bugs
> --
>
> Key: EAGLE-628
> URL: https://issues.apache.org/jira/browse/EAGLE-628
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> 1. when Site Id/Display Name/Description is missing, it will fail to create 
> site(filed of sql is missing).
> 2. configuration should be saved in applicationentity
> 3. enable update application entity
> 4. throw IllegalArgumentException("Duplicated appId), but table is empty



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-628) Fix jdbc metadata bugs

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-628:
--
Description: 
1. when Site Id/Display Name/Description is missing, it will fail to create 
site(some flelds of sql are missing).
2. configuration should be saved in applicationentity
3. enable update application entity
4. throw IllegalArgumentException("Duplicated appId), but table is empty

  was:
1. when Site Id/Display Name/Description is missing, it will fail to create 
site(filed of sql is missing).
2. configuration should be saved in applicationentity
3. enable update application entity
4. throw IllegalArgumentException("Duplicated appId), but table is empty


> Fix jdbc metadata bugs
> --
>
> Key: EAGLE-628
> URL: https://issues.apache.org/jira/browse/EAGLE-628
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> 1. when Site Id/Display Name/Description is missing, it will fail to create 
> site(some flelds of sql are missing).
> 2. configuration should be saved in applicationentity
> 3. enable update application entity
> 4. throw IllegalArgumentException("Duplicated appId), but table is empty



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-628) Fix jdbc metadata bugs

[wujinhu (JIRA)]

wujinhu created EAGLE-628:
-

 Summary: Fix jdbc metadata bugs
 Key: EAGLE-628
 URL: https://issues.apache.org/jira/browse/EAGLE-628
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


1. When Site Id/Display Name/Description is missing, it will fail to create 
site(filed of sql is missing).
2. configuration should be saved in applicationentity
3. enable update application entity



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-617) Scrollbar is missing when install Map Reduce History Job Monitoring

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-617.
-

> Scrollbar is missing when install Map Reduce History Job Monitoring
> ---
>
> Key: EAGLE-617
> URL: https://issues.apache.org/jira/browse/EAGLE-617
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: Jilin, Jiang
> Fix For: v0.5.0
>
>
> When I install Map Reduce History Job Monitoring and add new field 
> configures, Scrollbar is missing. My screen resolution is 2880 * 1800



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-527) Exception found when scan entity repositories

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-527.
-

> Exception found when scan entity repositories
> -
>
> Key: EAGLE-527
> URL: https://issues.apache.org/jira/browse/EAGLE-527
> Project: Eagle
>  Issue Type: Bug
>Reporter: wujinhu
>Assignee: Hao Chen
>
> 2016-09-06 00:15:22 Thread-6-mrHistoryJobExecutor 
> org.apache.eagle.jpm.mr.history.parser.JobEntityCreationEagleServiceListener 
> [INFO] flush JobExecutionAPIEntity of number 1
> 2016-09-06 00:15:22 Thread-6-mrHistoryJobExecutor 
> org.apache.eagle.log.entity.repo.EntityRepositoryScanner [INFO] Scanning all 
> entity repositories with pattern "org.apache.eagl
> e.*"
> 2016-09-06 00:15:23 eXtcos managed thread 1 
> net.sf.extcos.internal.JavaResourceAccessor [ERROR] Unable to read interface 
> [org.junit.runners.BlockJUnit4ClassRunner]
> 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-09-06 00:15:23 eXtcos managed thread 1 
> net.sf.extcos.internal.JavaResourceAccessor [ERROR] Unable to read super 
> class [org.junit.runners.BlockJUnit4ClassRunner]
> 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]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-618) migration eagle-jpm-aggregation to application framework

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-618.
-
Resolution: Resolved

> migration eagle-jpm-aggregation to application framework 
> -
>
> Key: EAGLE-618
> URL: https://issues.apache.org/jira/browse/EAGLE-618
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> We need migrate this application so that user can install it via ui.
> What need to do is add provider xml and spi to eagle-topology-assembly



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-618) migration eagle-jpm-aggregation to application framework

[wujinhu (JIRA)]

wujinhu created EAGLE-618:
-

 Summary: migration eagle-jpm-aggregation to application framework 
 Key: EAGLE-618
 URL: https://issues.apache.org/jira/browse/EAGLE-618
 Project: Eagle
  Issue Type: Improvement
Reporter: wujinhu
Assignee: wujinhu


We need migrate this application so that user can install it via ui.
What need to do is add provider xml and spi to eagle-topology-assembly



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-617) Scrollbar is missing when install Map Reduce History Job Monitoring

[wujinhu (JIRA)]

wujinhu created EAGLE-617:
-

 Summary: Scrollbar is missing when install Map Reduce History Job 
Monitoring
 Key: EAGLE-617
 URL: https://issues.apache.org/jira/browse/EAGLE-617
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: Jilin, Jiang
 Fix For: v0.5.0


When I install Map Reduce History Job Monitoring and add new field configures, 
Scrollbar is missing. My screen resolution is 2880 * 1800



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-605) Fix MR feeder provider.xml and remove useless configure

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-605.
-
Resolution: Fixed

> Fix MR feeder provider.xml and remove useless configure
> ---
>
> Key: EAGLE-605
> URL: https://issues.apache.org/jira/browse/EAGLE-605
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> 1. add missing configure from application.conf to provider.xml
> 2. remove useless configure like : 
> pathContainsJobTrackerName/jobTrackerName/dryRun



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-605) Fix MR feeder provider.xml and remove useless configure

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-605:
--
Description: 
1. add missing configure from application.conf to provider.xml
2. remove useless configure like : 
pathContainsJobTrackerName/jobTrackerName/dryRun

> Fix MR feeder provider.xml and remove useless configure
> ---
>
> Key: EAGLE-605
> URL: https://issues.apache.org/jira/browse/EAGLE-605
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> 1. add missing configure from application.conf to provider.xml
> 2. remove useless configure like : 
> pathContainsJobTrackerName/jobTrackerName/dryRun



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-605) Fix MR feeder provider.xml and remove useless configure

[wujinhu (JIRA)]

wujinhu created EAGLE-605:
-

 Summary: Fix MR feeder provider.xml and remove useless configure
 Key: EAGLE-605
 URL: https://issues.apache.org/jira/browse/EAGLE-605
 Project: Eagle
  Issue Type: Improvement
Reporter: wujinhu
Assignee: wujinhu






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-599) Some improvements when submit JPM applications

[wujinhu (JIRA)]

wujinhu created EAGLE-599:
-

 Summary: Some improvements when submit JPM applications
 Key: EAGLE-599
 URL: https://issues.apache.org/jira/browse/EAGLE-599
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: Jilin, Jiang
 Fix For: v0.5.0


1.  Some JPM applications have dynamic configures which are not contained in 
predefined configures, so WEB UI should support this function.
2.  It will convenient if user can submit a configure json.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-593) Eagle Topology assembly multi-version Hadoop support & bug fix

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-593.
-

> Eagle Topology assembly multi-version Hadoop support & bug fix
> --
>
> Key: EAGLE-593
> URL: https://issues.apache.org/jira/browse/EAGLE-593
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
>  Labels: app-framework
> Fix For: v0.5.0
>
>
> 1. User may want to support different version of hadoop in eagle jpm when 
> uses topology asembly to be a final package. For this requirement, we add 
> profiles to eagle-topology-assembly pom.xml. In this pom, we could add 
> different versions of Hadoop.
> 2. Fix StormSubmitter does not support submit another jar
> In storm StormSubmitter
> --
> private static String submittedJar = null;
> private static void submitJar(Map conf, ProgressListener listener) {
> if(submittedJar==null) {
> LOG.info("Jar not uploaded to master yet. Submitting jar...");
> String localJar = System.getProperty("storm.jar");
> submittedJar = submitJar(conf, localJar, listener);
> } else {
> LOG.info("Jar already uploaded to master. Not submitting jar.");
> }
> }
> --
> It can not submit another jar once submittedJar is set.
> So I rewrote this class.
> 3. Fix MR Running Job that does not set finished jobs' state



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-564) pack mr history/running feeder in one topology and bugs fix

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-564.
-
Resolution: Fixed

> pack mr history/running feeder in one topology and bugs fix
> ---
>
> Key: EAGLE-564
> URL: https://issues.apache.org/jira/browse/EAGLE-564
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> Pack MR history/Running feeder in the final topology by using 
> topology-assembly. 
> Changes:
> 1. remove useless configure
> 2. add application provider to topology assembly spi
> Bug fix:
> 1. Storm configure(workers/timeout...) does not overrided by customer defined 
> configure.
> 2. When install an application, user may not set jarPath, in this case, we 
> need to dynamic load, otherwise, use the jarPath that user provides.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-593) Eagle Topology assembly multi-version Hadoop support & bug fix

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-593:
--
Description: 
1. User may want to support different version of hadoop in eagle jpm when uses 
topology asembly to be a final package. For this requirement, we add profiles 
to eagle-topology-assembly pom.xml. In this pom, we could add different 
versions of Hadoop.
2. Fix StormSubmitter does not support submit another jar
In storm StormSubmitter
--
private static String submittedJar = null;
private static void submitJar(Map conf, ProgressListener listener) {
if(submittedJar==null) {
LOG.info("Jar not uploaded to master yet. Submitting jar...");
String localJar = System.getProperty("storm.jar");
submittedJar = submitJar(conf, localJar, listener);
} else {
LOG.info("Jar already uploaded to master. Not submitting jar.");
}
}
--
It can not submit another jar once submittedJar is set.
So I rewrote this class.
3. Fix MR Running Job that does not set finished jobs' state


  was:User may want to support different version of hadoop in eagle jpm. For 
this requirement, we add profiles to eagle-jpm pom.xml. In this pom, we could 
add different versions of Hadoop.


> Eagle Topology assembly multi-version Hadoop support & bug fix
> --
>
> Key: EAGLE-593
> URL: https://issues.apache.org/jira/browse/EAGLE-593
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> 1. User may want to support different version of hadoop in eagle jpm when 
> uses topology asembly to be a final package. For this requirement, we add 
> profiles to eagle-topology-assembly pom.xml. In this pom, we could add 
> different versions of Hadoop.
> 2. Fix StormSubmitter does not support submit another jar
> In storm StormSubmitter
> --
> private static String submittedJar = null;
> private static void submitJar(Map conf, ProgressListener listener) {
> if(submittedJar==null) {
> LOG.info("Jar not uploaded to master yet. Submitting jar...");
> String localJar = System.getProperty("storm.jar");
> submittedJar = submitJar(conf, localJar, listener);
> } else {
> LOG.info("Jar already uploaded to master. Not submitting jar.");
> }
> }
> --
> It can not submit another jar once submittedJar is set.
> So I rewrote this class.
> 3. Fix MR Running Job that does not set finished jobs' state



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-593) Eagle Topology assembly multi-version Hadoop support & bug fix

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-593:
--
Summary: Eagle Topology assembly multi-version Hadoop support & bug fix  
(was: Eagle JPM multi-version Hadoop support)

> Eagle Topology assembly multi-version Hadoop support & bug fix
> --
>
> Key: EAGLE-593
> URL: https://issues.apache.org/jira/browse/EAGLE-593
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> User may want to support different version of hadoop in eagle jpm. For this 
> requirement, we add profiles to eagle-jpm pom.xml. In this pom, we could add 
> different versions of Hadoop.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-518) add Job counter metrics for mr history job

[wujinhu (JIRA)]

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

wujinhu commented on EAGLE-518:
---

metric name is hadoop.job.day.count, it is a list of values.

> add Job counter metrics for mr history job
> --
>
> Key: EAGLE-518
> URL: https://issues.apache.org/jira/browse/EAGLE-518
> Project: Eagle
>  Issue Type: New Feature
>Reporter: wujinhu
>Assignee: wujinhu
>
> Add total/failed job count by each day.
> When the feeder finished processing one job, it saves the job status to 
> zookeeper and updates the total/failed job count to eagle server



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-496) Fix code style of JPM

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-496.
-
Resolution: Resolved

> Fix code style of JPM
> -
>
> Key: EAGLE-496
> URL: https://issues.apache.org/jira/browse/EAGLE-496
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> Fix code style of JPM



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (EAGLE-496) Fix code style of JPM

[wujinhu (JIRA)]

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

wujinhu reopened EAGLE-496:
---

> Fix code style of JPM
> -
>
> Key: EAGLE-496
> URL: https://issues.apache.org/jira/browse/EAGLE-496
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-496) Fix code style of JPM

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-496:
--
Description: Fix code style of JPM

> Fix code style of JPM
> -
>
> Key: EAGLE-496
> URL: https://issues.apache.org/jira/browse/EAGLE-496
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> Fix code style of JPM



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-276) JPM - Spark job history monitoring

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-276:
--
Description: 
We add the support for MR & Spark history job monitoring(JPM) for Apache Eagle 
which are used to analyze the performance of the history jobs and generate 
alerts. For now, they only contains data ingestion.

For MR JPM, it reads the finished job log files from hdfs, parses the log and 
configuration files and save the results to the backend storage. We use hbase 
now.

For Spark JPM, it fetches the finished job ids from the Resource manager,  asks 
the Spark history server for log file locations with the job ids, parses the 
log files and save the results to the backend storage which is hbase either.

To meet these requirements in a streaming way and achieve higher availability, 
both MR and Spark JPM use the storm topology. The spout reads MR history file 
logs or fetches Spark finished job ids from the Resource manager and the bolts 
handle the remaining logic.

We will add features about performance of history jobs and alerts later.

  was:
As administrator I want to monitor the spark job running in my cluster. Data of 
the follow jobs will be collected:

- Spark history jobs
- MR history jobs


> JPM - Spark job history monitoring
> -
>
> Key: EAGLE-276
> URL: https://issues.apache.org/jira/browse/EAGLE-276
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.4.0
>Reporter: Jing Ge
>Assignee: wujinhu
>  Labels: JPM
>
> We add the support for MR & Spark history job monitoring(JPM) for Apache 
> Eagle which are used to analyze the performance of the history jobs and 
> generate alerts. For now, they only contains data ingestion.
> For MR JPM, it reads the finished job log files from hdfs, parses the log and 
> configuration files and save the results to the backend storage. We use hbase 
> now.
> For Spark JPM, it fetches the finished job ids from the Resource manager,  
> asks the Spark history server for log file locations with the job ids, parses 
> the log files and save the results to the backend storage which is hbase 
> either.
> To meet these requirements in a streaming way and achieve higher 
> availability, both MR and Spark JPM use the storm topology. The spout reads 
> MR history file logs or fetches Spark finished job ids from the Resource 
> manager and the bolts handle the remaining logic.
> We will add features about performance of history jobs and alerts later.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-276) JPM - Spark job history monitoring

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-276.
-
Resolution: Resolved

> JPM - Spark job history monitoring
> -
>
> Key: EAGLE-276
> URL: https://issues.apache.org/jira/browse/EAGLE-276
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.4.0
>Reporter: Jing Ge
>Assignee: wujinhu
>  Labels: JPM
>
> We add the support for MR & Spark history job monitoring(JPM) for Apache 
> Eagle which are used to analyze the performance of the history jobs and 
> generate alerts. For now, they only contains data ingestion.
> For MR JPM, it reads the finished job log files from hdfs, parses the log and 
> configuration files and save the results to the backend storage. We use hbase 
> now.
> For Spark JPM, it fetches the finished job ids from the Resource manager,  
> asks the Spark history server for log file locations with the job ids, parses 
> the log files and save the results to the backend storage which is hbase 
> either.
> To meet these requirements in a streaming way and achieve higher 
> availability, both MR and Spark JPM use the storm topology. The spout reads 
> MR history file logs or fetches Spark finished job ids from the Resource 
> manager and the bolts handle the remaining logic.
> We will add features about performance of history jobs and alerts later.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-278) MR history jobs Feeder

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-278.
-

> MR history jobs Feeder
> --
>
> Key: EAGLE-278
> URL: https://issues.apache.org/jira/browse/EAGLE-278
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.4.0
>Reporter: Jing Ge
>Assignee: wujinhu
>  Labels: JPM
> Fix For: v0.5.0
>
>
> Both EAGLE-278 and EAGLE-277 are sub tasks of EAGLE-276. Please review 
> EAGLE-276.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (EAGLE-276) JPM - Spark job history monitoring

[wujinhu (JIRA)]

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

wujinhu reopened EAGLE-276:
---

> JPM - Spark job history monitoring
> -
>
> Key: EAGLE-276
> URL: https://issues.apache.org/jira/browse/EAGLE-276
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.4.0
>Reporter: Jing Ge
>Assignee: wujinhu
>  Labels: JPM
>
> As administrator I want to monitor the spark job running in my cluster. Data 
> of the follow jobs will be collected:
> - Spark history jobs
> - MR history jobs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-278) MR history jobs Feeder

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-278:
--
Description: Both EAGLE-278 and EAGLE-277 are sub tasks of EAGLE-276. 
Please review EAGLE-276.

> MR history jobs Feeder
> --
>
> Key: EAGLE-278
> URL: https://issues.apache.org/jira/browse/EAGLE-278
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.4.0
>Reporter: Jing Ge
>Assignee: wujinhu
>  Labels: JPM
> Fix For: v0.5.0
>
>
> Both EAGLE-278 and EAGLE-277 are sub tasks of EAGLE-276. Please review 
> EAGLE-276.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-277) Spark History jobs Feeder

[wujinhu (JIRA)]

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

wujinhu updated EAGLE-277:
--
Description: Both EAGLE-278 and EAGLE-277 are sub tasks of EAGLE-276. 
Please review EAGLE-276.

> Spark History jobs Feeder
> -
>
> Key: EAGLE-277
> URL: https://issues.apache.org/jira/browse/EAGLE-277
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.4.0
>Reporter: Jing Ge
>Assignee: wujinhu
>  Labels: JPM
> Fix For: v0.5.0
>
>
> Both EAGLE-278 and EAGLE-277 are sub tasks of EAGLE-276. Please review 
> EAGLE-276.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-593) Eagle JPM multi-version Hadoop support

[wujinhu (JIRA)]

wujinhu created EAGLE-593:
-

 Summary: Eagle JPM multi-version Hadoop support
 Key: EAGLE-593
 URL: https://issues.apache.org/jira/browse/EAGLE-593
 Project: Eagle
  Issue Type: Improvement
Reporter: wujinhu
Assignee: wujinhu


User may want to support different version of hadoop in eagle jpm. For this 
requirement, we add profiles to eagle-jpm pom.xml. In this pom, we could add 
different versions of Hadoop.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (EAGLE-361) Fix test building problem caused by kafka version and remove unused files

[wujinhu (JIRA)]

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

wujinhu reopened EAGLE-361:
---

> Fix test building problem caused by kafka version and remove unused files
> -
>
> Key: EAGLE-361
> URL: https://issues.apache.org/jira/browse/EAGLE-361
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-361) Fix test building problem caused by kafka version and remove unused files

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-361.
-
Resolution: Fixed

> Fix test building problem caused by kafka version and remove unused files
> -
>
> Key: EAGLE-361
> URL: https://issues.apache.org/jira/browse/EAGLE-361
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> Fix test building problem caused by kafka version and remove unused files



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)