[jira] [Commented] (EAGLE-673) add numOfPublishExecutors to alert engine topology

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-673:
--

GitHub user wujinhu opened a pull request:

https://github.com/apache/incubator-eagle/pull/555

[EAGLE-673] add numOfPublishExecutors to alert engine topology



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/wujinhu/incubator-eagle EAGLE-673

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/555.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #555


commit c82fe370ef20db5437f072bf25ec90f4f2917bba
Author: wujinhu 
Date:   2016-10-24T05:54:02Z

add numOfPublishExecutors to alert engine topology




> add numOfPublishExecutors 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 executors which will cause these tasks 
> are in only one bolt.



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

[GitHub] incubator-eagle pull request #555: [EAGLE-673] add numOfPublishExecutors to ...

[wujinhu]

GitHub user wujinhu opened a pull request:

https://github.com/apache/incubator-eagle/pull/555

[EAGLE-673] add numOfPublishExecutors to alert engine topology



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/wujinhu/incubator-eagle EAGLE-673

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/555.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #555


commit c82fe370ef20db5437f072bf25ec90f4f2917bba
Author: wujinhu 
Date:   2016-10-24T05:54:02Z

add numOfPublishExecutors to alert engine topology




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [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)

Re: Eagle graduation steps

[Edward Zhang]

I have verified the first 4 points in #1 preparations
  - update Eagle status page with latest information
http://incubator.apache.org/projects/eagle.html
  - name search was done last year with ticket solved
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-85
  - ability to create Apache releases, 2 releases was made,
https://github.com/apache/incubator-eagle/tree/branch-0.4 and
https://github.com/apache/incubator-eagle/tree/branch-0.3
  - community readiness. Some detailed information from Hao Chen
  1) Added *4+* new committers and *20+* contributors from
different organizations
around the world side
  2) Successfully released *2* major versions and some minor versions,
  3) resolved *632+* jira tickets and *577+* pull requests.
  4) *5+* public originations (e.g. eBay, Paypal, Yihaodian, Dataguise,
 etc.) are using or adopting eagle to monitor their hadoop clusters.
  5) Shared eagle and apache way in *10+* tech conferences in* 8+
*different cities around the world (e.g. Hadoop Summit, Hadoop Stratus,
QCon, etc.)


If you got time please review and give your feedback.
I will continue to check the rest of information.

Thanks
Edward

On Thu, Oct 20, 2016 at 9:01 PM, Edward Zhang 
wrote:

> I found the document about Apache project graduation steps, we can use
> that to graduate step by step.
>
> http://incubator.apache.org/guides/graduation.html
>
> I will update the status frequently on the following check list and will
> call for a VOTE if necessary.
>
> Graduation Check List
>
> The following is a short checklist giving an overview, not a substitute
> for reading the content below.
>
>1. Preparations
>   - Complete (and sign off) tasks documented in the status file
>   
>   - Ensure suitable names
>    for
>   project name and product names
>   - Demonstrate ability to create Apache releases
>   
>   - Demonstrate community readiness
>   
>   - Ensure Mentors
>   
> 
>and IPMC
>   
> 
>  have
>   no remaining issues
>   
>2. Decide upon destination
>
> 
>3. Prepare a resolution
> *(top
>level candidates only)*.
>4. Subproject acceptance VOTE
> 
> by
>destination Project *(subproject candidates only)*
>5. Incubator PMC (IPMC)
>
> 
>:
>   - For top level candidates, this is a recommendation VOTE
>   
> 
>   - For subproject candidates, this is a graduation approval VOTE
>   
> 
>6. Final hand-over
>
>7. Consider post graduation tasks
>
>
>

[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-671) AlertEngine: incorrect metric system use : too many metric object create and registered

[Zeng, Bryant (JIRA)]

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

Zeng, Bryant closed EAGLE-671.
--

> AlertEngine: incorrect metric system use : too many metric object create and 
> registered
> ---
>
> Key: EAGLE-671
> URL: https://issues.apache.org/jira/browse/EAGLE-671
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Zeng, Bryant
> Fix For: v0.5.0
>
>
> In AlertBolt: we should register one metric to metric system, then use the 
> metric object to send metric. Not  every-time register the metric to metric 
> systm.



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

[jira] [Resolved] (EAGLE-671) AlertEngine: incorrect metric system use : too many metric object create and registered

[Su Ralph (JIRA)]

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

Su Ralph resolved EAGLE-671.

Resolution: Fixed

Resolve as merged

> AlertEngine: incorrect metric system use : too many metric object create and 
> registered
> ---
>
> Key: EAGLE-671
> URL: https://issues.apache.org/jira/browse/EAGLE-671
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Zeng, Bryant
> Fix For: v0.5.0
>
>
> In AlertBolt: we should register one metric to metric system, then use the 
> metric object to send metric. Not  every-time register the metric to metric 
> systm.



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

[jira] [Commented] (EAGLE-671) AlertEngine: incorrect metric system use : too many metric object create and registered

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-671:
--

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/554


> AlertEngine: incorrect metric system use : too many metric object create and 
> registered
> ---
>
> Key: EAGLE-671
> URL: https://issues.apache.org/jira/browse/EAGLE-671
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Zeng, Bryant
> Fix For: v0.5.0
>
>
> In AlertBolt: we should register one metric to metric system, then use the 
> metric object to send metric. Not  every-time register the metric to metric 
> systm.



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

[GitHub] incubator-eagle pull request #554: EAGLE-671: incorrect metric system use : ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/554


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request #554: EAGLE-671: incorrect metric system use : ...

[mizeng]

GitHub user mizeng opened a pull request:

https://github.com/apache/incubator-eagle/pull/554

EAGLE-671: incorrect metric system use : too many metric object creat…

Currently there're too many metric objects create and registered in 
AlertBolt. This will impact the performance.

In AlertBolt: we should register one metric to metric system, then use the 
metric object to send metric. Not every-time register the metric to metric 
system.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mizeng/incubator-eagle master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/554.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #554


commit 5fd881a2eb7cd5750e1b1c52b12657c24491e77e
Author: mizeng 
Date:   2016-10-24T02:29:03Z

EAGLE-671: incorrect metric system use : too many metric object create and 
registered




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-671) AlertEngine: incorrect metric system use : too many metric object create and registered

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-671:
--

GitHub user mizeng opened a pull request:

https://github.com/apache/incubator-eagle/pull/554

EAGLE-671: incorrect metric system use : too many metric object creat…

Currently there're too many metric objects create and registered in 
AlertBolt. This will impact the performance.

In AlertBolt: we should register one metric to metric system, then use the 
metric object to send metric. Not every-time register the metric to metric 
system.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mizeng/incubator-eagle master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/554.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #554


commit 5fd881a2eb7cd5750e1b1c52b12657c24491e77e
Author: mizeng 
Date:   2016-10-24T02:29:03Z

EAGLE-671: incorrect metric system use : too many metric object create and 
registered




> AlertEngine: incorrect metric system use : too many metric object create and 
> registered
> ---
>
> Key: EAGLE-671
> URL: https://issues.apache.org/jira/browse/EAGLE-671
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Zeng, Bryant
> Fix For: v0.5.0
>
>
> In AlertBolt: we should register one metric to metric system, then use the 
> metric object to send metric. Not  every-time register the metric to metric 
> systm.



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

[jira] [Commented] (EAGLE-672) AlertEngine: MongoStateStore should be removed

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-672:
--

GitHub user garrettlish opened a pull request:

https://github.com/apache/incubator-eagle/pull/553

EAGLE-672: remove mongo state store for dedup

Currently the MongoStateStore is not a common use case for eagle, we need 
to remove the specific use case.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/garrettlish/incubator-eagle eagle672

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/553.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #553


commit 2d5a35e3b915651578f2764ffb99207504a8d4ca
Author: Xiancheng Li 
Date:   2016-10-24T01:32:21Z

EAGLE-672: remove mongo state store for dedup




> AlertEngine: MongoStateStore should be removed
> --
>
> Key: EAGLE-672
> URL: https://issues.apache.org/jira/browse/EAGLE-672
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> Below stack reported by Hao. We should not have mongo state store evolved in 
> deployment that doesn't have mongo enabled. And the class have too much 
> unreasonable hardcode field names. Please consider remove it.
> Stack:
> 2016-10-23 03:39:02 Thread-13 
> org.apache.eagle.alert.engine.publisher.dedup.MongoDedupEventsStore [ERROR] 
> find dedup state failed, but the state in memory is good, could be ingored.
> java.lang.NullPointerException: null
>at 
> org.apache.eagle.alert.engine.publisher.dedup.MongoDedupEventsStore.getEvents(MongoDedupEventsStore.java:102)
>  ~[stormjar.jar:na]
>at 
> org.apache.eagle.alert.engine.publisher.dedup.DedupCache.getEvents(DedupCache.java:103)
>  [stormjar.jar:na]
>at 
> org.apache.eagle.alert.engine.publisher.dedup.DedupCache$2.run(DedupCache.java:81)
>  [stormjar.jar:na]
>at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_91]
>at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_91]
>at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_91]
>at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  [na:1.8.0_91]
>at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_91]
>at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_91]
>at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]



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

[GitHub] incubator-eagle pull request #553: EAGLE-672: remove mongo state store for d...

[garrettlish]

GitHub user garrettlish opened a pull request:

https://github.com/apache/incubator-eagle/pull/553

EAGLE-672: remove mongo state store for dedup

Currently the MongoStateStore is not a common use case for eagle, we need 
to remove the specific use case.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/garrettlish/incubator-eagle eagle672

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/553.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #553


commit 2d5a35e3b915651578f2764ffb99207504a8d4ca
Author: Xiancheng Li 
Date:   2016-10-24T01:32:21Z

EAGLE-672: remove mongo state store for dedup




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (EAGLE-672) AlertEngine: MongoStateStore should be removed

[Su Ralph (JIRA)]

Su Ralph created EAGLE-672:
--

 Summary: AlertEngine: MongoStateStore should be removed
 Key: EAGLE-672
 URL: https://issues.apache.org/jira/browse/EAGLE-672
 Project: Eagle
  Issue Type: Task
Affects Versions: v0.5.0
Reporter: Su Ralph
Assignee: Garrett Li
 Fix For: v0.5.0


Below stack reported by Hao. We should not have mongo state store evolved in 
deployment that doesn't have mongo enabled. And the class have too much 
unreasonable hardcode field names. Please consider remove it.

Stack:

2016-10-23 03:39:02 Thread-13 
org.apache.eagle.alert.engine.publisher.dedup.MongoDedupEventsStore [ERROR] 
find dedup state failed, but the state in memory is good, could be ingored.
java.lang.NullPointerException: null
   at 
org.apache.eagle.alert.engine.publisher.dedup.MongoDedupEventsStore.getEvents(MongoDedupEventsStore.java:102)
 ~[stormjar.jar:na]
   at 
org.apache.eagle.alert.engine.publisher.dedup.DedupCache.getEvents(DedupCache.java:103)
 [stormjar.jar:na]
   at 
org.apache.eagle.alert.engine.publisher.dedup.DedupCache$2.run(DedupCache.java:81)
 [stormjar.jar:na]
   at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_91]
   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
[na:1.8.0_91]
   at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_91]
   at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 [na:1.8.0_91]
   at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_91]
   at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_91]
   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]





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

[jira] [Created] (EAGLE-671) AlertEngine: incorrect metric system use : too many metric object create and registered

[Su Ralph (JIRA)]

Su Ralph created EAGLE-671:
--

 Summary: AlertEngine: incorrect metric system use : too many 
metric object create and registered
 Key: EAGLE-671
 URL: https://issues.apache.org/jira/browse/EAGLE-671
 Project: Eagle
  Issue Type: Task
Affects Versions: v0.5.0
Reporter: Su Ralph
Assignee: Zeng, Bryant
 Fix For: v0.5.0


In AlertBolt: we should register one metric to metric system, then use the 
metric object to send metric. Not  every-time register the metric to metric 
systm.



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

[jira] [Created] (EAGLE-670) AlertEngine: Make Kafka Publisher configurable to async, for throughput tuning

[Su Ralph (JIRA)]

Su Ralph created EAGLE-670:
--

 Summary: AlertEngine: Make Kafka Publisher configurable to async, 
for throughput tuning
 Key: EAGLE-670
 URL: https://issues.apache.org/jira/browse/EAGLE-670
 Project: Eagle
  Issue Type: Task
Affects Versions: v0.5.0
Reporter: Su Ralph
Assignee: Garrett Li
 Fix For: v0.5.0


Kafka send alert in sync would limit the throughput. Make this configurable, 
and use async by default.



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

[GitHub] incubator-eagle pull request #552: [EAGLE-650] Hadoop JMX Metric Monitoring ...

[haoch]

GitHub user haoch opened a pull request:

https://github.com/apache/incubator-eagle/pull/552

[EAGLE-650] Hadoop JMX Metric Monitoring Application

Hadoop JMX Metric Monitoring Application

https://issues.apache.org/jira/browse/EAGLE-650

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/haoch/incubator-eagle EAGLE-650

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/552.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #552


commit de237f6a1d7f91177730778930173f2c1090b69a
Author: Hao Chen 
Date:   2016-10-23T17:38:49Z

Add static script-based HadoopMetricMonitorAppProvider




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Resolved] (EAGLE-665) Refactor kafka stream sink and hdfs audit topology using shuffle grouping

[Hao Chen (JIRA)]

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

Hao Chen resolved EAGLE-665.

Resolution: Fixed

> Refactor kafka stream sink and hdfs audit topology using shuffle grouping
> -
>
> Key: EAGLE-665
> URL: https://issues.apache.org/jira/browse/EAGLE-665
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Refactor kafka stream sink and hdfs audit topology using shuffle grouping



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