[jira] [Commented] (EAGLE-704) Update spark history config to integrate with the new application framework
[ https://issues.apache.org/jira/browse/EAGLE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624514#comment-15624514 ] ASF GitHub Bot commented on EAGLE-704: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/591 > Update spark history config to integrate with the new application framework > --- > > Key: EAGLE-704 > URL: https://issues.apache.org/jira/browse/EAGLE-704 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > This ticket will update SparkHistoryJobAppProvider.xml to integrate with > application framework. In this way, users can manage this topology on the web -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #591: EAGLE-704: Update spark history config to...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/591 --- 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-704) Update spark history config to integrate with the new application framework
[ https://issues.apache.org/jira/browse/EAGLE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624510#comment-15624510 ] ASF GitHub Bot commented on EAGLE-704: -- Github user qingwen220 commented on the issue: https://github.com/apache/incubator-eagle/pull/591 @wujinhu updated > Update spark history config to integrate with the new application framework > --- > > Key: EAGLE-704 > URL: https://issues.apache.org/jira/browse/EAGLE-704 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > This ticket will update SparkHistoryJobAppProvider.xml to integrate with > application framework. In this way, users can manage this topology on the web -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #591: EAGLE-704: Update spark history config to integr...
Github user qingwen220 commented on the issue: https://github.com/apache/incubator-eagle/pull/591 @wujinhu updated --- 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-704) Update spark history config to integrate with the new application framework
[ https://issues.apache.org/jira/browse/EAGLE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624394#comment-15624394 ] ASF GitHub Bot commented on EAGLE-704: -- Github user wujinhu commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/591#discussion_r85876370 --- Diff: eagle-jpm/eagle-jpm-spark-history/src/main/resources/META-INF/providers/org.apache.eagle.jpm.spark.history.SparkHistoryJobAppProvider.xml --- @@ -18,179 +18,127 @@ SPARK_HISTORY_JOB_APP -Spark History Job Monitoring +Spark History Job Monitor 0.5.0-incubating org.apache.eagle.jpm.spark.history.SparkHistoryJobApp - + -basic.cluster -cluster -Cluster Name -sandbox +workers +topology workers +topology workers +1 -basic.dataCenter -dataCenter -Data Center -sandbox +topology.numOfSpoutExecutors +spout executors +Parallelism of sparkHistoryJobFetchSpout +1 -basic.jobConf.additional.info -jobConf.additional.info -Additional info in Job Configs - +topology.numOfSpoutTasks +spout tasks +Tasks Num of sparkHistoryJobFetchSpout +4 + + +topology.numOfParseBoltExecutors +parser bolt parallelism hint +Parallelism of sparkHistoryJobParseBolt +1 + + +topology.numOfParserBoltTasks +parser bolt tasks +Tasks Num of sparkHistoryJobParseBolt +4 + + +topology.spoutCrawlInterval +spout crawl interval +Spout crawl interval (in milliseconds) +1 -dataSourceConfig.zkQuorum -zkQuorum -Zookeeper Quorum +topology.message.timeout.secs +topology message timeout (secs) +default timeout is 30s +300 + + + +zkStateConfig.zkQuorum +zookeeper quorum list +zookeeper to store topology metadata sandbox.hortonworks.com:2181 -dataSourceConfig.zkRoot -zkRoot +zkStateConfig.zkRoot +zookeeper root for topology metadata --- End diff -- This can hard code in source code, user does not need to know zkRoot details. > Update spark history config to integrate with the new application framework > --- > > Key: EAGLE-704 > URL: https://issues.apache.org/jira/browse/EAGLE-704 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > This ticket will update SparkHistoryJobAppProvider.xml to integrate with > application framework. In this way, users can manage this topology on the web -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-704) Update spark history config to integrate with the new application framework
[ https://issues.apache.org/jira/browse/EAGLE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624397#comment-15624397 ] ASF GitHub Bot commented on EAGLE-704: -- Github user wujinhu commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/591#discussion_r85876408 --- Diff: eagle-jpm/eagle-jpm-spark-history/src/main/resources/META-INF/providers/org.apache.eagle.jpm.spark.history.SparkHistoryJobAppProvider.xml --- @@ -18,179 +18,127 @@ SPARK_HISTORY_JOB_APP -Spark History Job Monitoring +Spark History Job Monitor 0.5.0-incubating org.apache.eagle.jpm.spark.history.SparkHistoryJobApp - + -basic.cluster -cluster -Cluster Name -sandbox +workers +topology workers +topology workers +1 -basic.dataCenter -dataCenter -Data Center -sandbox +topology.numOfSpoutExecutors +spout executors +Parallelism of sparkHistoryJobFetchSpout +1 -basic.jobConf.additional.info -jobConf.additional.info -Additional info in Job Configs - +topology.numOfSpoutTasks +spout tasks +Tasks Num of sparkHistoryJobFetchSpout +4 + + +topology.numOfParseBoltExecutors +parser bolt parallelism hint +Parallelism of sparkHistoryJobParseBolt +1 + + +topology.numOfParserBoltTasks +parser bolt tasks +Tasks Num of sparkHistoryJobParseBolt +4 + + +topology.spoutCrawlInterval +spout crawl interval +Spout crawl interval (in milliseconds) +1 -dataSourceConfig.zkQuorum -zkQuorum -Zookeeper Quorum +topology.message.timeout.secs +topology message timeout (secs) +default timeout is 30s +300 + + + +zkStateConfig.zkQuorum +zookeeper quorum list +zookeeper to store topology metadata sandbox.hortonworks.com:2181 -dataSourceConfig.zkRoot -zkRoot +zkStateConfig.zkRoot +zookeeper root for topology metadata Zookeeper Root /sparkHistoryJob -dataSourceConfig.zkPort -zkPort -Zookeeper Port -2181 - - -dataSourceConfig.zkSessionTimeoutMs -zkSessionTimeoutMs +zkStateConfig.zkSessionTimeoutMs +zookeeper session timeout (ms) Zookeeper session timeoutMs 15000 -zookeeperConfig.zkRetryTimes -zkRetryTimes -zookeeperConfig.zkRetryTimes +zkStateConfig.zkRetryTimes +zookeeper connection retry times +retry times for zookeeper connection 3 -zookeeperConfig.zkRetryInterval -zkRetryInterval -zookeeperConfig.zkRetryInterval +zkStateConfig.zkRetryInterval +zookeeper connection retry interval +retry interval for zookeeper connection 2 + + dataSourceConfig.spark.history.server.url -spark.history.server.url -Spark History Server URL +spark history server url +spark history server URL http://sandbox.hortonworks.com:18080 +true dataSourceConfig.spark.history.server.username -spark.history.server.username -Spark History Server Auth Username +user name for spark history server +spark history server auth username --- End diff -- It seems we do not use spark history server now, the codes have been commented > Update spark history config to integrate with the new application framework > --
[GitHub] incubator-eagle pull request #591: EAGLE-704: Update spark history config to...
Github user wujinhu commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/591#discussion_r85876408 --- Diff: eagle-jpm/eagle-jpm-spark-history/src/main/resources/META-INF/providers/org.apache.eagle.jpm.spark.history.SparkHistoryJobAppProvider.xml --- @@ -18,179 +18,127 @@ SPARK_HISTORY_JOB_APP -Spark History Job Monitoring +Spark History Job Monitor 0.5.0-incubating org.apache.eagle.jpm.spark.history.SparkHistoryJobApp - + -basic.cluster -cluster -Cluster Name -sandbox +workers +topology workers +topology workers +1 -basic.dataCenter -dataCenter -Data Center -sandbox +topology.numOfSpoutExecutors +spout executors +Parallelism of sparkHistoryJobFetchSpout +1 -basic.jobConf.additional.info -jobConf.additional.info -Additional info in Job Configs - +topology.numOfSpoutTasks +spout tasks +Tasks Num of sparkHistoryJobFetchSpout +4 + + +topology.numOfParseBoltExecutors +parser bolt parallelism hint +Parallelism of sparkHistoryJobParseBolt +1 + + +topology.numOfParserBoltTasks +parser bolt tasks +Tasks Num of sparkHistoryJobParseBolt +4 + + +topology.spoutCrawlInterval +spout crawl interval +Spout crawl interval (in milliseconds) +1 -dataSourceConfig.zkQuorum -zkQuorum -Zookeeper Quorum +topology.message.timeout.secs +topology message timeout (secs) +default timeout is 30s +300 + + + +zkStateConfig.zkQuorum +zookeeper quorum list +zookeeper to store topology metadata sandbox.hortonworks.com:2181 -dataSourceConfig.zkRoot -zkRoot +zkStateConfig.zkRoot +zookeeper root for topology metadata Zookeeper Root /sparkHistoryJob -dataSourceConfig.zkPort -zkPort -Zookeeper Port -2181 - - -dataSourceConfig.zkSessionTimeoutMs -zkSessionTimeoutMs +zkStateConfig.zkSessionTimeoutMs +zookeeper session timeout (ms) Zookeeper session timeoutMs 15000 -zookeeperConfig.zkRetryTimes -zkRetryTimes -zookeeperConfig.zkRetryTimes +zkStateConfig.zkRetryTimes +zookeeper connection retry times +retry times for zookeeper connection 3 -zookeeperConfig.zkRetryInterval -zkRetryInterval -zookeeperConfig.zkRetryInterval +zkStateConfig.zkRetryInterval +zookeeper connection retry interval +retry interval for zookeeper connection 2 + + dataSourceConfig.spark.history.server.url -spark.history.server.url -Spark History Server URL +spark history server url +spark history server URL http://sandbox.hortonworks.com:18080 +true dataSourceConfig.spark.history.server.username -spark.history.server.username -Spark History Server Auth Username +user name for spark history server +spark history server auth username --- End diff -- It seems we do not use spark history server now, the codes have been commented --- 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-704) Update spark history config to integrate with the new application framework
[ https://issues.apache.org/jira/browse/EAGLE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624392#comment-15624392 ] ASF GitHub Bot commented on EAGLE-704: -- Github user wujinhu commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/591#discussion_r85876323 --- Diff: eagle-jpm/eagle-jpm-spark-history/src/main/resources/META-INF/providers/org.apache.eagle.jpm.spark.history.SparkHistoryJobAppProvider.xml --- @@ -18,179 +18,127 @@ SPARK_HISTORY_JOB_APP -Spark History Job Monitoring +Spark History Job Monitor 0.5.0-incubating org.apache.eagle.jpm.spark.history.SparkHistoryJobApp - + -basic.cluster -cluster -Cluster Name -sandbox +workers +topology workers +topology workers +1 -basic.dataCenter -dataCenter -Data Center -sandbox +topology.numOfSpoutExecutors +spout executors +Parallelism of sparkHistoryJobFetchSpout +1 -basic.jobConf.additional.info -jobConf.additional.info -Additional info in Job Configs - +topology.numOfSpoutTasks +spout tasks +Tasks Num of sparkHistoryJobFetchSpout +4 + + +topology.numOfParseBoltExecutors +parser bolt parallelism hint +Parallelism of sparkHistoryJobParseBolt +1 + + +topology.numOfParserBoltTasks +parser bolt tasks +Tasks Num of sparkHistoryJobParseBolt +4 + + +topology.spoutCrawlInterval +spout crawl interval +Spout crawl interval (in milliseconds) +1 -dataSourceConfig.zkQuorum -zkQuorum -Zookeeper Quorum +topology.message.timeout.secs +topology message timeout (secs) +default timeout is 30s +300 + + + +zkStateConfig.zkQuorum +zookeeper quorum list +zookeeper to store topology metadata --- End diff -- zookeeper configure is in eagle server config, we can reuse > Update spark history config to integrate with the new application framework > --- > > Key: EAGLE-704 > URL: https://issues.apache.org/jira/browse/EAGLE-704 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > This ticket will update SparkHistoryJobAppProvider.xml to integrate with > application framework. In this way, users can manage this topology on the web -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #591: EAGLE-704: Update spark history config to...
Github user wujinhu commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/591#discussion_r85876370 --- Diff: eagle-jpm/eagle-jpm-spark-history/src/main/resources/META-INF/providers/org.apache.eagle.jpm.spark.history.SparkHistoryJobAppProvider.xml --- @@ -18,179 +18,127 @@ SPARK_HISTORY_JOB_APP -Spark History Job Monitoring +Spark History Job Monitor 0.5.0-incubating org.apache.eagle.jpm.spark.history.SparkHistoryJobApp - + -basic.cluster -cluster -Cluster Name -sandbox +workers +topology workers +topology workers +1 -basic.dataCenter -dataCenter -Data Center -sandbox +topology.numOfSpoutExecutors +spout executors +Parallelism of sparkHistoryJobFetchSpout +1 -basic.jobConf.additional.info -jobConf.additional.info -Additional info in Job Configs - +topology.numOfSpoutTasks +spout tasks +Tasks Num of sparkHistoryJobFetchSpout +4 + + +topology.numOfParseBoltExecutors +parser bolt parallelism hint +Parallelism of sparkHistoryJobParseBolt +1 + + +topology.numOfParserBoltTasks +parser bolt tasks +Tasks Num of sparkHistoryJobParseBolt +4 + + +topology.spoutCrawlInterval +spout crawl interval +Spout crawl interval (in milliseconds) +1 -dataSourceConfig.zkQuorum -zkQuorum -Zookeeper Quorum +topology.message.timeout.secs +topology message timeout (secs) +default timeout is 30s +300 + + + +zkStateConfig.zkQuorum +zookeeper quorum list +zookeeper to store topology metadata sandbox.hortonworks.com:2181 -dataSourceConfig.zkRoot -zkRoot +zkStateConfig.zkRoot +zookeeper root for topology metadata --- End diff -- This can hard code in source code, user does not need to know zkRoot details. --- 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 #591: EAGLE-704: Update spark history config to...
Github user wujinhu commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/591#discussion_r85876323 --- Diff: eagle-jpm/eagle-jpm-spark-history/src/main/resources/META-INF/providers/org.apache.eagle.jpm.spark.history.SparkHistoryJobAppProvider.xml --- @@ -18,179 +18,127 @@ SPARK_HISTORY_JOB_APP -Spark History Job Monitoring +Spark History Job Monitor 0.5.0-incubating org.apache.eagle.jpm.spark.history.SparkHistoryJobApp - + -basic.cluster -cluster -Cluster Name -sandbox +workers +topology workers +topology workers +1 -basic.dataCenter -dataCenter -Data Center -sandbox +topology.numOfSpoutExecutors +spout executors +Parallelism of sparkHistoryJobFetchSpout +1 -basic.jobConf.additional.info -jobConf.additional.info -Additional info in Job Configs - +topology.numOfSpoutTasks +spout tasks +Tasks Num of sparkHistoryJobFetchSpout +4 + + +topology.numOfParseBoltExecutors +parser bolt parallelism hint +Parallelism of sparkHistoryJobParseBolt +1 + + +topology.numOfParserBoltTasks +parser bolt tasks +Tasks Num of sparkHistoryJobParseBolt +4 + + +topology.spoutCrawlInterval +spout crawl interval +Spout crawl interval (in milliseconds) +1 -dataSourceConfig.zkQuorum -zkQuorum -Zookeeper Quorum +topology.message.timeout.secs +topology message timeout (secs) +default timeout is 30s +300 + + + +zkStateConfig.zkQuorum +zookeeper quorum list +zookeeper to store topology metadata --- End diff -- zookeeper configure is in eagle server config, we can reuse --- 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-715) optimize some configurations for alert
[ https://issues.apache.org/jira/browse/EAGLE-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624330#comment-15624330 ] ASF GitHub Bot commented on EAGLE-715: -- GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/592 [EAGLE-715] optimize some configurations for alert You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-715 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/592.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 #592 commit 9667bee2a6c4fcc45373a4dba0653b435c8db7ab Author: wujinhu Date: 2016-11-01T04:36:24Z optimize some configurations for alert > 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)
[GitHub] incubator-eagle pull request #592: [EAGLE-715] optimize some configurations ...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/592 [EAGLE-715] optimize some configurations for alert You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-715 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/592.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 #592 commit 9667bee2a6c4fcc45373a4dba0653b435c8db7ab Author: wujinhu Date: 2016-11-01T04:36:24Z optimize some configurations for alert --- 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-713) Publish & Router bolts spec change is not thread safe
[ https://issues.apache.org/jira/browse/EAGLE-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624315#comment-15624315 ] ASF GitHub Bot commented on EAGLE-713: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/590 > Publish & Router bolts spec change is not thread safe > - > > Key: EAGLE-713 > URL: https://issues.apache.org/jira/browse/EAGLE-713 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > Publish & Router bolts spec change is not thread safe, 2 concurrent spec > change event will causes the policy has duplicated publishment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #590: EAGLE-713: Publish & Router bolts spec ch...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/590 --- 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] [Closed] (EAGLE-561) JsonMappingException in Hadoop queue feeder
[ https://issues.apache.org/jira/browse/EAGLE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-561. > JsonMappingException in Hadoop queue feeder > --- > > Key: EAGLE-561 > URL: https://issues.apache.org/jira/browse/EAGLE-561 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Michael Wu > Fix For: v0.5.0 > > > This exception is caused by a yarn rest api bug: > https://issues.apache.org/jira/browse/YARN-4785 > the "type" field for LeafQueueInfo in response of RM REST API has > inconsistent value type ( String and Array ) . While String type is expected -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-704) Update spark history config to integrate with the new application framework
[ https://issues.apache.org/jira/browse/EAGLE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624288#comment-15624288 ] ASF GitHub Bot commented on EAGLE-704: -- GitHub user qingwen220 opened a pull request: https://github.com/apache/incubator-eagle/pull/591 EAGLE-704: Update spark history config to integrate with the new application framework https://issues.apache.org/jira/browse/EAGLE-704 You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/incubator-eagle EAGLE-704 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/591.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 #591 commit 9e4a3f2dbac08d093c6f4d8980199e9e99110f20 Author: Zhao, Qingwen Date: 2016-10-31T13:14:54Z convert spark history job commit 9083d659193739e9fa1b5b26bb57f5bb05932bbf Author: Zhao, Qingwen Date: 2016-11-01T03:00:51Z update SparkHistoryJobAppConfig > Update spark history config to integrate with the new application framework > --- > > Key: EAGLE-704 > URL: https://issues.apache.org/jira/browse/EAGLE-704 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > This ticket will update SparkHistoryJobAppProvider.xml to integrate with > application framework. In this way, users can manage this topology on the web -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-681) Add new publisher AlertEagleStorePlugin
[ https://issues.apache.org/jira/browse/EAGLE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-681. --- Resolution: Done > Add new publisher AlertEagleStorePlugin > > > Key: EAGLE-681 > URL: https://issues.apache.org/jira/browse/EAGLE-681 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > Fix For: v0.5.0 > > > In Eagle 0.5, only three types of publishers supported: email, kafka, slack. > Users may be want to view all the alerts on the web, which requires eagle to > store the alert into database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-557) Setup Eagle v0.5 Documentation Site Layout
[ https://issues.apache.org/jira/browse/EAGLE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu resolved EAGLE-557. -- Resolution: Fixed > Setup Eagle v0.5 Documentation Site Layout > -- > > Key: EAGLE-557 > URL: https://issues.apache.org/jira/browse/EAGLE-557 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Michael Wu > Fix For: v0.5.0 > > > * Setup initial doc structure with mkdocs, provide basic content proposal and > some manual docs about how to add new docs. > * Setup a mkdocs service on demo node, listening on port 8000. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-563) Refactor Hadoop queue feeder using application framework
[ https://issues.apache.org/jira/browse/EAGLE-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu resolved EAGLE-563. -- Resolution: Fixed > Refactor Hadoop queue feeder using application framework > > > Key: EAGLE-563 > URL: https://issues.apache.org/jira/browse/EAGLE-563 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Michael Wu > > Currently hadoop queue feeder is developed as independent storm application. > In order to make sure hadoop queue feeder could be well managed by > application framework and service -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-557) Setup Eagle v0.5 Documentation Site Layout
[ https://issues.apache.org/jira/browse/EAGLE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-557. > Setup Eagle v0.5 Documentation Site Layout > -- > > Key: EAGLE-557 > URL: https://issues.apache.org/jira/browse/EAGLE-557 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Michael Wu > Fix For: v0.5.0 > > > * Setup initial doc structure with mkdocs, provide basic content proposal and > some manual docs about how to add new docs. > * Setup a mkdocs service on demo node, listening on port 8000. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-561) JsonMappingException in Hadoop queue feeder
[ https://issues.apache.org/jira/browse/EAGLE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu resolved EAGLE-561. -- Resolution: Fixed > JsonMappingException in Hadoop queue feeder > --- > > Key: EAGLE-561 > URL: https://issues.apache.org/jira/browse/EAGLE-561 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Michael Wu > Fix For: v0.5.0 > > > This exception is caused by a yarn rest api bug: > https://issues.apache.org/jira/browse/YARN-4785 > the "type" field for LeafQueueInfo in response of RM REST API has > inconsistent value type ( String and Array ) . While String type is expected -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-563) Refactor Hadoop queue feeder using application framework
[ https://issues.apache.org/jira/browse/EAGLE-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-563. > Refactor Hadoop queue feeder using application framework > > > Key: EAGLE-563 > URL: https://issues.apache.org/jira/browse/EAGLE-563 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Michael Wu > > Currently hadoop queue feeder is developed as independent storm application. > In order to make sure hadoop queue feeder could be well managed by > application framework and service -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-685) adjust hadoop-queue application configuration parameters according to classified style
[ https://issues.apache.org/jira/browse/EAGLE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu closed EAGLE-685. > adjust hadoop-queue application configuration parameters according to > classified style > -- > > Key: EAGLE-685 > URL: https://issues.apache.org/jira/browse/EAGLE-685 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > > application configuration has been divided into a few sections based on > parameter type > need to adjust code to fit for the change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-685) adjust hadoop-queue application configuration parameters according to classified style
[ https://issues.apache.org/jira/browse/EAGLE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Wu resolved EAGLE-685. -- Resolution: Fixed > adjust hadoop-queue application configuration parameters according to > classified style > -- > > Key: EAGLE-685 > URL: https://issues.apache.org/jira/browse/EAGLE-685 > Project: Eagle > Issue Type: Task >Reporter: Michael Wu >Assignee: Michael Wu > > application configuration has been divided into a few sections based on > parameter type > need to adjust code to fit for the change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #591: EAGLE-704: Update spark history config to...
GitHub user qingwen220 opened a pull request: https://github.com/apache/incubator-eagle/pull/591 EAGLE-704: Update spark history config to integrate with the new application framework https://issues.apache.org/jira/browse/EAGLE-704 You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/incubator-eagle EAGLE-704 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/591.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 #591 commit 9e4a3f2dbac08d093c6f4d8980199e9e99110f20 Author: Zhao, Qingwen Date: 2016-10-31T13:14:54Z convert spark history job commit 9083d659193739e9fa1b5b26bb57f5bb05932bbf Author: Zhao, Qingwen Date: 2016-11-01T03:00:51Z update SparkHistoryJobAppConfig --- 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 #588: [EAGLE-705] streams is null when call /re...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/588 --- 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-705) streams is null when call /rest/apps/ api
[ https://issues.apache.org/jira/browse/EAGLE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624256#comment-15624256 ] ASF GitHub Bot commented on EAGLE-705: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/588 > 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] [Commented] (EAGLE-713) Publish & Router bolts spec change is not thread safe
[ https://issues.apache.org/jira/browse/EAGLE-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624271#comment-15624271 ] ASF GitHub Bot commented on EAGLE-713: -- GitHub user garrettlish opened a pull request: https://github.com/apache/incubator-eagle/pull/590 EAGLE-713: Publish & Router bolts spec change is not thread safe Publish & Router bolts spec change is not thread safe, 2 concurrent spec change event will causes the policy has duplicated publishment. You can merge this pull request into a Git repository by running: $ git pull https://github.com/garrettlish/incubator-eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/590.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 #590 commit 721801939aaa92dc4b9dca5c1f9f28072fd9b917 Author: Xiancheng Li Date: 2016-11-01T02:55:28Z EAGLE-713: Publish & Router bolts spec change is not thread safe > Publish & Router bolts spec change is not thread safe > - > > Key: EAGLE-713 > URL: https://issues.apache.org/jira/browse/EAGLE-713 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > Publish & Router bolts spec change is not thread safe, 2 concurrent spec > change event will causes the policy has duplicated publishment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #590: EAGLE-713: Publish & Router bolts spec ch...
GitHub user garrettlish opened a pull request: https://github.com/apache/incubator-eagle/pull/590 EAGLE-713: Publish & Router bolts spec change is not thread safe Publish & Router bolts spec change is not thread safe, 2 concurrent spec change event will causes the policy has duplicated publishment. You can merge this pull request into a Git repository by running: $ git pull https://github.com/garrettlish/incubator-eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/590.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 #590 commit 721801939aaa92dc4b9dca5c1f9f28072fd9b917 Author: Xiancheng Li Date: 2016-11-01T02:55:28Z EAGLE-713: Publish & Router bolts spec change is not thread safe --- 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 #589: Eagle-714 Application improvement
GitHub user zombieJ opened a pull request: https://github.com/apache/incubator-eagle/pull/589 Eagle-714 Application improvement * Application detail page display as `N/A` * use 2 line of input field (jarPath) You can merge this pull request into a Git repository by running: $ git pull https://github.com/zombieJ/incubator-eagle EAGLE-714 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/589.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 #589 commit 345d78abf76723cbb5b3641180513b60ff9e8c77 Author: zombieJ Date: 2016-11-01T03:11:07Z add naBlock directive commit 54f054289a2e78ce9a1dd3aa51724ed5df1955b7 Author: zombieJ Date: 2016-11-01T03:32:07Z always require publisher of policy --- 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-715) optimize some configurations for alert
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] [Commented] (EAGLE-705) streams is null when call /rest/apps/ api
[ https://issues.apache.org/jira/browse/EAGLE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624200#comment-15624200 ] ASF GitHub Bot commented on EAGLE-705: -- Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/588 LGTM > 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)
[GitHub] incubator-eagle issue #588: [EAGLE-705] streams is null when call /rest/apps...
Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/588 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 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-714) Application improvement
Jilin, Jiang created EAGLE-714: -- Summary: Application improvement Key: EAGLE-714 URL: https://issues.apache.org/jira/browse/EAGLE-714 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Jilin, Jiang Assignee: Jilin, Jiang Priority: Critical Fix For: v0.5.0 * Application detail page display as `N/A` * use 2 line of input field (jarPath) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-705) streams is null when call /rest/apps/ api
[ 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-713) Publish & Router bolts spec change is not thread safe
Garrett Li created EAGLE-713: Summary: Publish & Router bolts spec change is not thread safe Key: EAGLE-713 URL: https://issues.apache.org/jira/browse/EAGLE-713 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Garrett Li Assignee: Garrett Li Fix For: v0.5.0 Publish & Router bolts spec change is not thread safe, 2 concurrent spec change event will causes the policy has duplicated publishment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-712) Document HDFS audit log monitoring application (DAM)
[ https://issues.apache.org/jira/browse/EAGLE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jianzhong.chen updated EAGLE-712: - Assignee: Zhao, Qingwen (was: Hao Chen) > Document HDFS audit log monitoring application (DAM) > > > Key: EAGLE-712 > URL: https://issues.apache.org/jira/browse/EAGLE-712 > Project: Eagle > Issue Type: Task >Reporter: jianzhong.chen >Assignee: Zhao, Qingwen > Labels: docuentation > Fix For: v0.5.0 > > > Application description along with: > - what to be monitored > - how to collect data, any expected impact to monitored service > - how to define a policy, especially on how to extract the fields from > stream? > - as much as supported policy examples > - latency expected for alert > - how to troubleshooting an application if any failure happens? > - .. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-712) Document HDFS audit log monitoring application (DAM)
jianzhong.chen created EAGLE-712: Summary: Document HDFS audit log monitoring application (DAM) Key: EAGLE-712 URL: https://issues.apache.org/jira/browse/EAGLE-712 Project: Eagle Issue Type: Task Reporter: jianzhong.chen Assignee: Hao Chen Fix For: v0.5.0 Application description along with: - what to be monitored - how to collect data, any expected impact to monitored service - how to define a policy, especially on how to extract the fields from stream? - as much as supported policy examples - latency expected for alert - how to troubleshooting an application if any failure happens? - .. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-711) Document JMX monitoring application
jianzhong.chen created EAGLE-711: Summary: Document JMX monitoring application Key: EAGLE-711 URL: https://issues.apache.org/jira/browse/EAGLE-711 Project: Eagle Issue Type: Task Reporter: jianzhong.chen Assignee: yupu Fix For: v0.5.0 Application description along with: - what to be monitored - how to collect data, any expected impact to monitored service - how to define a policy, especially on how to extract the fields from stream? - as much as supported policy examples - latency expected for alert - how to troubleshooting an application if any failure happens? - .. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-711) Document JMX monitoring application
[ https://issues.apache.org/jira/browse/EAGLE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jianzhong.chen updated EAGLE-711: - Assignee: Hao Chen (was: yupu) > Document JMX monitoring application > --- > > Key: EAGLE-711 > URL: https://issues.apache.org/jira/browse/EAGLE-711 > Project: Eagle > Issue Type: Task >Reporter: jianzhong.chen >Assignee: Hao Chen > Labels: docuentation > Fix For: v0.5.0 > > > Application description along with: > - what to be monitored > - how to collect data, any expected impact to monitored service > - how to define a policy, especially on how to extract the fields from > stream? > - as much as supported policy examples > - latency expected for alert > - how to troubleshooting an application if any failure happens? > - .. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-710) Document service health check application
[ https://issues.apache.org/jira/browse/EAGLE-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jianzhong.chen updated EAGLE-710: - Assignee: yupu (was: wujinhu) > Document service health check application > - > > Key: EAGLE-710 > URL: https://issues.apache.org/jira/browse/EAGLE-710 > Project: Eagle > Issue Type: Task >Reporter: jianzhong.chen >Assignee: yupu > Labels: docuentation > Fix For: v0.5.0 > > > Application description along with: > - what to be monitored > - how to collect data, any expected impact to monitored service > - how to define a policy, especially on how to extract the fields from > stream? > - as much as supported policy examples > - latency expected for alert > - how to troubleshooting an application if any failure happens? > - .. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-710) Document service health check application
jianzhong.chen created EAGLE-710: Summary: Document service health check application Key: EAGLE-710 URL: https://issues.apache.org/jira/browse/EAGLE-710 Project: Eagle Issue Type: Task Reporter: jianzhong.chen Assignee: wujinhu Fix For: v0.5.0 Application description along with: - what to be monitored - how to collect data, any expected impact to monitored service - how to define a policy, especially on how to extract the fields from stream? - as much as supported policy examples - latency expected for alert - how to troubleshooting an application if any failure happens? - .. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-709) Document job performance monitoring application
jianzhong.chen created EAGLE-709: Summary: Document job performance monitoring application Key: EAGLE-709 URL: https://issues.apache.org/jira/browse/EAGLE-709 Project: Eagle Issue Type: Task Reporter: jianzhong.chen Assignee: wujinhu Fix For: v0.5.0 Application description along with: - what to be monitored - how to collect data, any expected impact to monitored service - how to define a policy, especially on how to extract the fields from stream? - as much as supported policy examples - latency expected for alert - how to troubleshooting an application if any failure happens? - .. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Podling Report Reminder - November 2016
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 16 November 2016, 10:30 am PDT. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, November 02). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/November2016 Note: This is manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
[jira] [Created] (EAGLE-708) document the Apache Eagle deployment from scratch
jianzhong.chen created EAGLE-708: Summary: document the Apache Eagle deployment from scratch Key: EAGLE-708 URL: https://issues.apache.org/jira/browse/EAGLE-708 Project: Eagle Issue Type: Task Reporter: jianzhong.chen Assignee: wujinhu Fix For: v0.5.0 We should have a documentation about how to setup an Apache Eagle environment from scratch, the OS and its configuration, the external dependencies, versions, configuration, .. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-707) Mark "Task Statistic" page title as "Task Statistic (Beta)" instead of "(beta) Task Statistic"
jianzhong.chen created EAGLE-707: Summary: Mark "Task Statistic" page title as "Task Statistic (Beta)" instead of "(beta) Task Statistic" Key: EAGLE-707 URL: https://issues.apache.org/jira/browse/EAGLE-707 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: jianzhong.chen Assignee: Jilin, Jiang Fix For: v0.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Consider highlighting your podling at ApacheCON in Seville
Hi! with ApacheCON in Seville right around the corner chances are you've made your travel arrangements already. If you happen to be around the conference on Fri, November 18th, 16:30 - 17:20 why not use that time to highlight your favorite podling? https://s.apache.org/aceu2016_shark_tank Podling Shark Tank is back and it is a perfect opportunity to give a short, 5 min pitch in a fun environment. You don't have to be a committer on the project, or even a developer! All you have to have is a bit of free time and a lot of passion to let the world know how awesome this project is! If you feel interested -- please either sign up on the wiki page (it also provides more details on the event) https://wiki.apache.org/apachecon/Seville16PodlingSharkTank or just reply to this thread. Either way -- hope to see you at Podling Shark Tank in Seville! Thanks, Roman.
[jira] [Commented] (EAGLE-705) streams is null when call /rest/apps/ api
[ https://issues.apache.org/jira/browse/EAGLE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15622402#comment-15622402 ] ASF GitHub Bot commented on EAGLE-705: -- GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/588 [EAGLE-705] streams is null when call /rest/apps/ api You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-705 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/588.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 #588 commit e850305302e7cac1371cd71445795b19fc8edea0 Author: wujinhu Date: 2016-10-31T14:59:20Z streams is null when call /rest/apps/ api > 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)
[GitHub] incubator-eagle pull request #588: [EAGLE-705] streams is null when call /re...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/588 [EAGLE-705] streams is null when call /rest/apps/ api You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-705 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/588.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 #588 commit e850305302e7cac1371cd71445795b19fc8edea0 Author: wujinhu Date: 2016-10-31T14:59:20Z streams is null when call /rest/apps/ api --- 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-706) Policy UI adv mode support sql highlight
[ https://issues.apache.org/jira/browse/EAGLE-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621742#comment-15621742 ] ASF GitHub Bot commented on EAGLE-706: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/587 > Policy UI adv mode support sql highlight > > > Key: EAGLE-706 > URL: https://issues.apache.org/jira/browse/EAGLE-706 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang >Priority: Minor > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #587: EAGLE-706 Policy UI adv mode support sql ...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/587 --- 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 issue #587: EAGLE-706 Policy UI adv mode support sql highlig...
Github user qingwen220 commented on the issue: https://github.com/apache/incubator-eagle/pull/587 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 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-706) Policy UI adv mode support sql highlight
[ https://issues.apache.org/jira/browse/EAGLE-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621736#comment-15621736 ] ASF GitHub Bot commented on EAGLE-706: -- Github user qingwen220 commented on the issue: https://github.com/apache/incubator-eagle/pull/587 LTGM > Policy UI adv mode support sql highlight > > > Key: EAGLE-706 > URL: https://issues.apache.org/jira/browse/EAGLE-706 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang >Priority: Minor > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-706) Policy UI adv mode support sql highlight
[ https://issues.apache.org/jira/browse/EAGLE-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621737#comment-15621737 ] ASF GitHub Bot commented on EAGLE-706: -- Github user qingwen220 commented on the issue: https://github.com/apache/incubator-eagle/pull/587 LGTM > Policy UI adv mode support sql highlight > > > Key: EAGLE-706 > URL: https://issues.apache.org/jira/browse/EAGLE-706 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang >Priority: Minor > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #587: EAGLE-706 Policy UI adv mode support sql highlig...
Github user qingwen220 commented on the issue: https://github.com/apache/incubator-eagle/pull/587 LTGM --- 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-698) Help eagle to collect system and Hadoop JMX information
[ https://issues.apache.org/jira/browse/EAGLE-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621722#comment-15621722 ] ASF GitHub Bot commented on EAGLE-698: -- Github user joe-hj commented on the issue: https://github.com/apache/incubator-eagle/pull/584 Sorry for the title issue, had updated > Help eagle to collect system and Hadoop JMX information > --- > > Key: EAGLE-698 > URL: https://issues.apache.org/jira/browse/EAGLE-698 > Project: Eagle > Issue Type: New Feature >Affects Versions: v0.5.0 >Reporter: juhe >Assignee: juhe > Fix For: v0.5.0 > > > Integrated collect and kafka plugin to gather system information and Hadoop > JMX information , and write to kafka cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #584: [EAGLE-698] Collectd python plugin for gathering...
Github user joe-hj commented on the issue: https://github.com/apache/incubator-eagle/pull/584 Sorry for the title issue, had updated --- 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 #587: EAGLE-706 Policy UI adv mode support sql ...
GitHub user zombieJ opened a pull request: https://github.com/apache/incubator-eagle/pull/587 EAGLE-706 Policy UI adv mode support sql highlight Add ace editor to make policy edit page sql highlight You can merge this pull request into a Git repository by running: $ git pull https://github.com/zombieJ/incubator-eagle highlight Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/587.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 #587 commit af097a5204fa30125c237b2ad38a9581d732b0c2 Author: zombieJ Date: 2016-10-31T03:25:11Z support default value template of application commit 34eaf5963c1a5b0378e4895338d989fc2587211b Author: zombieJ Date: 2016-10-31T03:41:12Z confirm dialog of start / stop application commit 88f6102350e3c7db56df60d71168d06b8a29493e Author: zombieJ Date: 2016-10-31T07:11:56Z ace commit e916407529235f961b98ebe800818841f615f7d6 Author: zombieJ Date: 2016-10-31T09:09:29Z support polict adv edit commit 21ba8c85a4a81db71f2ffdb3b2f2e3998413e959 Author: zombieJ Date: 2016-10-31T09:21:52Z opt the update logic of editor update --- 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-706) Policy UI adv mode support sql highlight
[ https://issues.apache.org/jira/browse/EAGLE-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621704#comment-15621704 ] ASF GitHub Bot commented on EAGLE-706: -- GitHub user zombieJ opened a pull request: https://github.com/apache/incubator-eagle/pull/587 EAGLE-706 Policy UI adv mode support sql highlight Add ace editor to make policy edit page sql highlight You can merge this pull request into a Git repository by running: $ git pull https://github.com/zombieJ/incubator-eagle highlight Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/587.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 #587 commit af097a5204fa30125c237b2ad38a9581d732b0c2 Author: zombieJ Date: 2016-10-31T03:25:11Z support default value template of application commit 34eaf5963c1a5b0378e4895338d989fc2587211b Author: zombieJ Date: 2016-10-31T03:41:12Z confirm dialog of start / stop application commit 88f6102350e3c7db56df60d71168d06b8a29493e Author: zombieJ Date: 2016-10-31T07:11:56Z ace commit e916407529235f961b98ebe800818841f615f7d6 Author: zombieJ Date: 2016-10-31T09:09:29Z support polict adv edit commit 21ba8c85a4a81db71f2ffdb3b2f2e3998413e959 Author: zombieJ Date: 2016-10-31T09:21:52Z opt the update logic of editor update > Policy UI adv mode support sql highlight > > > Key: EAGLE-706 > URL: https://issues.apache.org/jira/browse/EAGLE-706 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang >Priority: Minor > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-706) Policy UI adv mode support sql highlight
Jilin, Jiang created EAGLE-706: -- Summary: Policy UI adv mode support sql highlight Key: EAGLE-706 URL: https://issues.apache.org/jira/browse/EAGLE-706 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Jilin, Jiang Assignee: Jilin, Jiang Priority: Minor Fix For: v0.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-705) streams is null when call /rest/apps/ api
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)
[GitHub] incubator-eagle pull request #586: [EAGLE-701] AlertEngine: bolt should chec...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/586 --- 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-701) AlertEngine: bolt should check ZK for latest spec when start
[ https://issues.apache.org/jira/browse/EAGLE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621676#comment-15621676 ] ASF GitHub Bot commented on EAGLE-701: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/586 > AlertEngine: bolt should check ZK for latest spec when start > > > Key: EAGLE-701 > URL: https://issues.apache.org/jira/browse/EAGLE-701 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: wujinhu > Fix For: v0.5.0 > > > Currently, bolt use zk listening for metadata reload only. > This require zk to be periodically updated. In the case of bolt down, and > storm start bolt another place(vm, process), if the zk is not updated, then > new bolt possibly can not get the metadata to work well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-701) AlertEngine: bolt should check ZK for latest spec when start
[ https://issues.apache.org/jira/browse/EAGLE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-701. - Resolution: Fixed > AlertEngine: bolt should check ZK for latest spec when start > > > Key: EAGLE-701 > URL: https://issues.apache.org/jira/browse/EAGLE-701 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: wujinhu > Fix For: v0.5.0 > > > Currently, bolt use zk listening for metadata reload only. > This require zk to be periodically updated. In the case of bolt down, and > storm start bolt another place(vm, process), if the zk is not updated, then > new bolt possibly can not get the metadata to work well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-701) AlertEngine: bolt should check ZK for latest spec when start
[ https://issues.apache.org/jira/browse/EAGLE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621609#comment-15621609 ] ASF GitHub Bot commented on EAGLE-701: -- GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/586 [EAGLE-701] AlertEngine: bolt should check ZK for latest spec when start You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-701 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/586.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 #586 commit bd6ac1d74a6c71bf7bde8046c06266c0afeb1988 Author: wujinhu Date: 2016-10-31T08:28:35Z AlertEngine: bolt should check ZK for latest spec when start > AlertEngine: bolt should check ZK for latest spec when start > > > Key: EAGLE-701 > URL: https://issues.apache.org/jira/browse/EAGLE-701 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: wujinhu > Fix For: v0.5.0 > > > Currently, bolt use zk listening for metadata reload only. > This require zk to be periodically updated. In the case of bolt down, and > storm start bolt another place(vm, process), if the zk is not updated, then > new bolt possibly can not get the metadata to work well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #586: [EAGLE-701] AlertEngine: bolt should chec...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/586 [EAGLE-701] AlertEngine: bolt should check ZK for latest spec when start You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-701 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/586.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 #586 commit bd6ac1d74a6c71bf7bde8046c06266c0afeb1988 Author: wujinhu Date: 2016-10-31T08:28:35Z AlertEngine: bolt should check ZK for latest spec when start --- 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-704) Update spark history config to integrate with the new application framework
Zhao, Qingwen created EAGLE-704: --- Summary: Update spark history config to integrate with the new application framework Key: EAGLE-704 URL: https://issues.apache.org/jira/browse/EAGLE-704 Project: Eagle Issue Type: Improvement Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen This ticket will update SparkHistoryJobAppProvider.xml to integrate with application framework. In this way, users can manage this topology on the web -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-696) Improve HdfsAuditLogApplication & AlertUnitTopologyApp config
[ https://issues.apache.org/jira/browse/EAGLE-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao, Qingwen closed EAGLE-696. --- Resolution: Done > Improve HdfsAuditLogApplication & AlertUnitTopologyApp config > -- > > Key: EAGLE-696 > URL: https://issues.apache.org/jira/browse/EAGLE-696 > Project: Eagle > Issue Type: Improvement >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > add field display name & refactor the configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332)