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

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

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

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 G

[jira] [Commented] (EAGLE-650) Hadoop JMX Metric Monitoring Application

[ https://issues.apache.org/jira/browse/EAGLE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15600041#comment-15600041 ] ASF GitHub Bot commented on EAGLE-650: -- GitHub user haoch opened a pull request:

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

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

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

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: Eagl

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

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 V

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

[ https://issues.apache.org/jira/browse/EAGLE-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15600646#comment-15600646 ] ASF GitHub Bot commented on EAGLE-672: -- GitHub user garrettlish opened a pull request:

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

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

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

[ https://issues.apache.org/jira/browse/EAGLE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15600747#comment-15600747 ] ASF GitHub Bot commented on EAGLE-671: -- GitHub user mizeng opened a pull request:

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

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.

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

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 featur

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

[ https://issues.apache.org/jira/browse/EAGLE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15600756#comment-15600756 ] ASF GitHub Bot commented on EAGLE-671: -- Github user asfgit closed the pull request at:

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

[ 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 crea

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

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

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

[ https://issues.apache.org/jira/browse/EAGLE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15600784#comment-15600784 ] wujinhu commented on EAGLE-146: --- I researched this issue and it was caused by storm installat

Re: Eagle graduation steps

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 re

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

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 Vers

[GitHub] incubator-eagle pull request #:

Github user haoch commented on the pull request: https://github.com/apache/incubator-eagle/commit/56e7048ff75a9d8865173961e1537daf18eeb41c#commitcomment-19535240 LGTM. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If y

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

[ https://issues.apache.org/jira/browse/EAGLE-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu updated EAGLE-673: -- Summary: add numOfPublishExecutors to alert engine topology (was: add numOfPublishBolts to alert engine topology

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

[ https://issues.apache.org/jira/browse/EAGLE-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu updated EAGLE-673: -- Description: When creates alert engine topology BoltDeclarer boltDeclarer = builder.setBolt(alertPublishB

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

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

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

[ https://issues.apache.org/jira/browse/EAGLE-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601047#comment-15601047 ] ASF GitHub Bot commented on EAGLE-673: -- GitHub user wujinhu opened a pull request:

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

Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/555 --- 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 featur

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

[ https://issues.apache.org/jira/browse/EAGLE-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601070#comment-15601070 ] ASF GitHub Bot commented on EAGLE-673: -- Github user asfgit closed the pull request at:

[GitHub] incubator-eagle pull request #556: EAGLE-670: make kafka publisher configura...

GitHub user garrettlish opened a pull request: https://github.com/apache/incubator-eagle/pull/556 EAGLE-670: make kafka publisher configurable and default is async Kafka send alert in sync would limit the throughput. Make this configurable, and use async by default You can merge th

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

[ https://issues.apache.org/jira/browse/EAGLE-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601074#comment-15601074 ] ASF GitHub Bot commented on EAGLE-670: -- GitHub user garrettlish opened a pull request:

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

[ https://issues.apache.org/jira/browse/EAGLE-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-673. - Resolution: Fixed > add numOfPublishExecutors to alert engine topology > --

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

Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/553 --- 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 featur

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

[ https://issues.apache.org/jira/browse/EAGLE-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601088#comment-15601088 ] ASF GitHub Bot commented on EAGLE-672: -- Github user asfgit closed the pull request at:

[GitHub] incubator-eagle issue #556: EAGLE-670: make kafka publisher configurable and...

Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/556 @garrettlish the implementation looks a little confusing. Please just simply use kafka configs: https://kafka.apache.org/08/documentation.html#clientconfig and another part using asyn

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

[ https://issues.apache.org/jira/browse/EAGLE-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601091#comment-15601091 ] ASF GitHub Bot commented on EAGLE-670: -- Github user haoch commented on the issue:

[GitHub] incubator-eagle issue #556: EAGLE-670: make kafka publisher configurable and...

Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/556 The convention here: we will have these properties as part of publishment and need to avoid "." in key, since mongo store doesn't support "." in key, use "_" instead. There

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

[ https://issues.apache.org/jira/browse/EAGLE-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601121#comment-15601121 ] ASF GitHub Bot commented on EAGLE-670: -- Github user RalphSu commented on the issue: