[jira] [Created] (EAGLE-842) mr running job count in zookeeper does not match the number in hbase
wujinhu created EAGLE-842: - Summary: mr running job count in zookeeper does not match the number in hbase Key: EAGLE-842 URL: https://issues.apache.org/jira/browse/EAGLE-842 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: wujinhu Assignee: Lingang Deng Fix For: v0.5.0 As you know, we save running job basic information in zookeeper and will be moved when the job finished. However, as time goes on, some running job basic information still exists in zookeeper, and when you run the zookeeper command get /apps/mr/running/sandbox in zk shell, the number increases slowly. You can compare this with the RUNNING number in JPM Web widget. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-841) CorrelationSpout reads kafkaBrokerZkQuorum from datasource first
wujinhu created EAGLE-841: - Summary: CorrelationSpout reads kafkaBrokerZkQuorum from datasource first Key: EAGLE-841 URL: https://issues.apache.org/jira/browse/EAGLE-841 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 CorrelationSpout reads kafkaBrokerZkQuorum from datasource first -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-840) Task Failing Nodes List and bad node detection
wujinhu created EAGLE-840: - Summary: Task Failing Nodes List and bad node detection Key: EAGLE-840 URL: https://issues.apache.org/jira/browse/EAGLE-840 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 add Task Failing Nodes List and bad node detection -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-839) add job diagnostics
wujinhu created EAGLE-839: - Summary: add job diagnostics Key: EAGLE-839 URL: https://issues.apache.org/jira/browse/EAGLE-839 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 When job failed, get job diagnostics from JobUnsuccessfulCompletion event. But the diagnostics from JobUnsuccessfulCompletion is simple, we format it by using task attempt error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-835) Job failure diagnostics and Bad node detection
wujinhu created EAGLE-835: - Summary: Job failure diagnostics and Bad node detection Key: EAGLE-835 URL: https://issues.apache.org/jira/browse/EAGLE-835 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 1. Job failure diagnostics (task failure category) 2. Task Failing Nodes List and bad node detection Based on pre-aggregated the same as job failure diagnostics -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-827) Coordinator schedule time out
wujinhu created EAGLE-827: - Summary: Coordinator schedule time out Key: EAGLE-827 URL: https://issues.apache.org/jira/browse/EAGLE-827 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: wujinhu Assignee: Garrett Li Fix For: v0.5.0 Coordinator schedule time out(fail to get exclusive lock) because of last fail -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-826) Coordinator throws NullPointerException when generateSpoutMonitorMetadata
wujinhu created EAGLE-826: - Summary: Coordinator throws NullPointerException when generateSpoutMonitorMetadata Key: EAGLE-826 URL: https://issues.apache.org/jira/browse/EAGLE-826 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: wujinhu Assignee: Garrett Li Fix For: v0.5.0 Coordinator throws NullPointerException when generateSpoutMonitorMetadata because data source is empty, should catch this exception -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-821) coordinator bug in alert engine
wujinhu created EAGLE-821: - Summary: coordinator bug in alert engine Key: EAGLE-821 URL: https://issues.apache.org/jira/browse/EAGLE-821 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: wujinhu Assignee: Zhao, Qingwen Fix For: v0.5.0 Coordinator has bugs below: 1. When I disable a policy, coordinator does not clear allocated queue 2. Coordinator can not schedule policies while there are alert bolts with no resources 3. When I create some policies with stream A and B, coordinator can not schedule policy with stream C although there are free resources How to reproduce: Create 8 or more policies with stream A and some policies with Stream B, then create policy with steam C, will reproduce 2 and 3(the number may depends). When you see all the alert bolts contains stream A, then disable policy with stream A, it will reproduce 1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-817) add KillOptions when stop a topology
wujinhu created EAGLE-817: - Summary: add KillOptions when stop a topology Key: EAGLE-817 URL: https://issues.apache.org/jira/browse/EAGLE-817 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 add KillOptions when stop a topology avoid waiting killed topology disappear from storm cluster -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-814) fix alertId is null in AlertStreamEvent bug
wujinhu created EAGLE-814: - Summary: fix alertId is null in AlertStreamEvent bug Key: EAGLE-814 URL: https://issues.apache.org/jira/browse/EAGLE-814 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 alertId is null when call notifyAlert() 2016-11-29 02:42:34 Thread-18-alertPublishBolt org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl [ERROR] Fail invoking publisher's onAlert, continue java.lang.IllegalArgumentException: data may not be null at org.apache.commons.httpclient.util.EncodingUtil.getBytes(EncodingUtil.java:203) ~[stormjar.jar:na] at org.apache.commons.httpclient.util.URIUtil.encode(URIUtil.java:502) ~[stormjar.jar:na] at org.apache.commons.httpclient.util.URIUtil.encodeQuery(URIUtil.java:468) ~[stormjar.jar:na] at org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.buildAlertContext(AlertEmailGenerator.java:130) ~[stormjar.jar:na] at org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:64) ~[stormjar.jar:na] at org.apache.eagle.alert.engine.publisher.email.AlertEmailGenerator.sendAlertEmail(AlertEmailGenerator.java:55) ~[stormjar.jar:na] at org.apache.eagle.alert.engine.publisher.impl.AlertEmailPublisher.onAlert(AlertEmailPublisher.java:84) ~[stormjar.jar:na] at org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:87) [stormjar.jar:na] at org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.nextEvent(AlertPublisherImpl.java:70) [stormjar.jar:na] at org.apache.eagle.alert.engine.runner.AlertPublisherBolt.execute(AlertPublisherBolt.java:84) [stormjar.jar:na] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-787) add healthy check for hadoop-queue/topology-health/spark-history apps
wujinhu created EAGLE-787: - Summary: add healthy check for hadoop-queue/topology-health/spark-history apps Key: EAGLE-787 URL: https://issues.apache.org/jira/browse/EAGLE-787 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 add healthy check for hadoop-queue/topology-health/spark-history apps -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-779) add a managed task to regularly schedule registered healthchecks
[ https://issues.apache.org/jira/browse/EAGLE-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-779. - Resolution: Resolved > add a managed task to regularly schedule registered healthchecks > > > Key: EAGLE-779 > URL: https://issues.apache.org/jira/browse/EAGLE-779 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > add a managed task to regularly schedule registered healthchecks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #657: [EAGLE-779] add a managed task to regular...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/657 [EAGLE-779] add a managed task to regularly schedule registered healthchecks You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-779 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/657.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 #657 commit 9978491765d15159c038300d3786f36e061cfae2 Author: wujinhu <wujinhu...@126.com> Date: 2016-11-16T05:34:35Z add a managed task to regularly schedule registered healthchecks --- 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-779) add a managed task to regularly schedule registered healthchecks
wujinhu created EAGLE-779: - Summary: add a managed task to regularly schedule registered healthchecks Key: EAGLE-779 URL: https://issues.apache.org/jira/browse/EAGLE-779 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 add a managed task to regularly schedule registered healthchecks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-772) simply refactor mr running job feeder
wujinhu created EAGLE-772: - Summary: simply refactor mr running job feeder Key: EAGLE-772 URL: https://issues.apache.org/jira/browse/EAGLE-772 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 Currently, both MRRunningJobFetchSpout and MRRunningJobParseBolt try to delete application from zookeeper, the two threads probably delete the same applications. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-770) remove InterProcessMutex from JobHistoryZKStateManager
[ https://issues.apache.org/jira/browse/EAGLE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-770. - Resolution: Fixed > remove InterProcessMutex from JobHistoryZKStateManager > -- > > Key: EAGLE-770 > URL: https://issues.apache.org/jira/browse/EAGLE-770 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > InterProcessMutex works across JVMs. But our applications are running in > storm cluster, a storm worker may contains many task threads. So that the > lock is useless. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-770) remove InterProcessMutex from JobHistoryZKStateManager
[ https://issues.apache.org/jira/browse/EAGLE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu updated EAGLE-770: -- Summary: remove InterProcessMutex from JobHistoryZKStateManager (was: remove InterProcessMutex from JobHistoryZKStateManager) > remove InterProcessMutex from JobHistoryZKStateManager > -- > > Key: EAGLE-770 > URL: https://issues.apache.org/jira/browse/EAGLE-770 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > InterProcessMutex works across JVMs. But our applications are running in > storm cluster, a storm worker may contains many task threads. So that the > lock is useless. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-770) remove InterProcessMutex from JobHistoryZKStateManager
[ https://issues.apache.org/jira/browse/EAGLE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu updated EAGLE-770: -- Summary: remove InterProcessMutex from JobHistoryZKStateManager (was: remove InterProcessMutex from JobHistoryZKStateManager) > remove InterProcessMutex from JobHistoryZKStateManager > > > Key: EAGLE-770 > URL: https://issues.apache.org/jira/browse/EAGLE-770 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > InterProcessMutex works across JVMs. But our applications are running in > storm cluster, a storm worker may contains many task threads. So that the > lock is useless. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #655: [EAGLE-770] remove InterProcessMutex from...
GitHub user wujinhu reopened a pull request: https://github.com/apache/incubator-eagle/pull/655 [EAGLE-770] remove InterProcessMutex from JobHistoryZKStateManager You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-770 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/655.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 #655 commit 890648662e1a4398de46a4925869d56f4e4135a4 Author: wujinhu <wujinhu...@126.com> Date: 2016-11-15T08:48:11Z remove InterProcessMutex from JobHistoryZKStateManager commit e4c9c58fc533f7374f05f9b662e89bd98daf6d60 Author: wujinhu <wujinhu...@126.com> Date: 2016-11-15T08:50:08Z remove InterProcessMutex from JobHistoryZKStateManager --- 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 #655: [EAGLE-770] remove InterProcessMutex from...
Github user wujinhu closed the pull request at: https://github.com/apache/incubator-eagle/pull/655 --- 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 #655: [EAGLE-770] remove InterProcessMutex from...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/655 [EAGLE-770] remove InterProcessMutex from JobHistoryZKStateManager You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-770 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/655.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 #655 commit 890648662e1a4398de46a4925869d56f4e4135a4 Author: wujinhu <wujinhu...@126.com> Date: 2016-11-15T08:48:11Z remove InterProcessMutex from JobHistoryZKStateManager commit e4c9c58fc533f7374f05f9b662e89bd98daf6d60 Author: wujinhu <wujinhu...@126.com> Date: 2016-11-15T08:50:08Z remove InterProcessMutex from JobHistoryZKStateManager --- 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-770) remove InterProcessMutex from JobHistoryZKStateManager
wujinhu created EAGLE-770: - Summary: remove InterProcessMutex from JobHistoryZKStateManager Key: EAGLE-770 URL: https://issues.apache.org/jira/browse/EAGLE-770 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 InterProcessMutex works across JVMs. But our applications are running in storm cluster, a storm worker may contains many task threads. So that the lock is useless. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #653: [MINOR] Move getHealthCheck from Applicat...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/653 [MINOR] Move getHealthCheck from Application to ApplicationProvider You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle HealthCheck Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/653.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 #653 commit 25dcb91d63297e575fa3294b88763af61bc8d3d4 Author: wujinhu <wujinhu...@126.com> Date: 2016-11-15T06:08:31Z Move getHealthCheck from Application to ApplicationProvider --- 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 #652: [EAGLE-764] MR history feeder support Health Che...
Github user wujinhu commented on the issue: https://github.com/apache/incubator-eagle/pull/652 Fixed --- 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-764) MR history feeder support Health Checks
[ https://issues.apache.org/jira/browse/EAGLE-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-764. - Resolution: Fixed > MR history feeder support Health Checks > --- > > Key: EAGLE-764 > URL: https://issues.apache.org/jira/browse/EAGLE-764 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > MR history feeder support Health Checks > Use Application Health Checks with DropWizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #652: [EAGLE-764] MR history feeder support Hea...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/652 [EAGLE-764] MR history feeder support Health Checks You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-764 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/652.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 #652 commit bf7c54ece4b504e7a448f3b9cf768a63cc8c Author: wujinhu <wujinhu...@126.com> Date: 2016-11-15T03:52:41Z MR history feeder support Health Checks --- 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-764) MR history feeder support Health Checks
wujinhu created EAGLE-764: - Summary: MR history feeder support Health Checks Key: EAGLE-764 URL: https://issues.apache.org/jira/browse/EAGLE-764 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 MR history feeder support Health Checks Use Application Health Checks with DropWizard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-757) fix alert JdbcDatabaseHandler connection issue
[ https://issues.apache.org/jira/browse/EAGLE-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-757. - Resolution: Fixed > fix alert JdbcDatabaseHandler connection issue > -- > > Key: EAGLE-757 > URL: https://issues.apache.org/jira/browse/EAGLE-757 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > 1. fix JdbcDatabaseHandler connection, could not share one connection > 2. remove code like e.printStackTrace(); use log instead -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #648: [EAGLE-757] fix alert JdbcDatabaseHandler...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/648 [EAGLE-757] fix alert JdbcDatabaseHandler connection issue You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-757 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/648.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 #648 commit 2dc4bbdbb6427d566411de9a59a3fd922661b83e Author: wujinhu <wujinhu...@126.com> Date: 2016-11-13T12:28:18Z fix alert JdbcDatabaseHandler connection issue commit 0eb2deda42d941f1cb61d5fdc4e4fb7daf890126 Author: wujinhu <wujinhu...@126.com> Date: 2016-11-13T12:42:08Z Merge branch 'master' of https://github.com/apache/incubator-eagle into EAGLE-757 # Conflicts: # eagle-core/eagle-metadata/eagle-metadata-jdbc/src/main/java/org/apache/eagle/metadata/store/jdbc/JDBCDataSourceConfig.java --- 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-742) check applications when remove site
[
https://issues.apache.org/jira/browse/EAGLE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wujinhu closed EAGLE-742.
-
Resolution: Fixed
> check applications when remove site
> ---
>
> Key: EAGLE-742
> URL: https://issues.apache.org/jira/browse/EAGLE-742
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
> Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> When we want to remove site through rest api(below two), we need to check
> applications. If applications number is not zero, then remove failed.
> Web ui should check success whether it is false or true
> @DELETE
> @Path("/{siteId}")
> @Produces(MediaType.APPLICATION_JSON)
> public RESTResponse deleteSiteBySiteId(@PathParam("siteId")
> String siteId){
> }
> @DELETE
> @Consumes(MediaType.APPLICATION_JSON)
> @Produces(MediaType.APPLICATION_JSON)
> public RESTResponse deleteSiteByUUID(UUIDRequest uuidRequest){
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-eagle issue #635: Eagle-759 Policy detail support alert list
Github user wujinhu commented on the issue: https://github.com/apache/incubator-eagle/pull/635 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-757) fix alert JdbcDatabaseHandler connection issue
wujinhu created EAGLE-757: - Summary: fix alert JdbcDatabaseHandler connection issue Key: EAGLE-757 URL: https://issues.apache.org/jira/browse/EAGLE-757 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 1. fix JdbcDatabaseHandler connection, could not share one connection 2. remove code like e.printStackTrace(); use log instead -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #615: [EAGLE-742] check applications when remov...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/615 [EAGLE-742] check applications when remove site You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-742 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/615.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 #615 commit cd66b1c5017223b2b95382ea0dc92e247513c788 Author: wujinhu <wujinhu...@126.com> Date: 2016-11-07T08:43:25Z check applications when remove site --- 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-745) web ui should check success(true or false) when delete site
wujinhu created EAGLE-745: - Summary: web ui should check success(true or false) when delete site Key: EAGLE-745 URL: https://issues.apache.org/jira/browse/EAGLE-745 Project: Eagle Issue Type: Sub-task Affects Versions: v0.5.0 Reporter: wujinhu Assignee: Jilin, Jiang Fix For: v0.5.0 web ui should check success(true or false) when delete site -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-742) check applications when remove site
[
https://issues.apache.org/jira/browse/EAGLE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wujinhu updated EAGLE-742:
--
Description:
When we want to remove site through rest api(below two), we need to check
applications. If applications number is not zero, then remove failed.
Web ui should check success whether it is false or true
@DELETE
@Path("/{siteId}")
@Produces(MediaType.APPLICATION_JSON)
public RESTResponse deleteSiteBySiteId(@PathParam("siteId") String
siteId){
}
@DELETE
@Consumes(MediaType.APPLICATION_JSON)
@Produces(MediaType.APPLICATION_JSON)
public RESTResponse deleteSiteByUUID(UUIDRequest uuidRequest){
}
was:When we want to remove site, we need to check applications. If
applications number is not zero, then remove failed.
> check applications when remove site
> ---
>
> Key: EAGLE-742
> URL: https://issues.apache.org/jira/browse/EAGLE-742
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
> Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> When we want to remove site through rest api(below two), we need to check
> applications. If applications number is not zero, then remove failed.
> Web ui should check success whether it is false or true
> @DELETE
> @Path("/{siteId}")
> @Produces(MediaType.APPLICATION_JSON)
> public RESTResponse deleteSiteBySiteId(@PathParam("siteId")
> String siteId){
> }
> @DELETE
> @Consumes(MediaType.APPLICATION_JSON)
> @Produces(MediaType.APPLICATION_JSON)
> public RESTResponse deleteSiteByUUID(UUIDRequest uuidRequest){
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-742) check applications when remove site
[ https://issues.apache.org/jira/browse/EAGLE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu updated EAGLE-742: -- Description: When we want to remove site, we need to check applications. If applications number is not zero, then remove failed. (was: When site has been removed, streams defined are still there. We need remove them.) > check applications when remove site > --- > > Key: EAGLE-742 > URL: https://issues.apache.org/jira/browse/EAGLE-742 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > When we want to remove site, we need to check applications. If applications > number is not zero, then remove failed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-742) check applications when remove site
[ https://issues.apache.org/jira/browse/EAGLE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu updated EAGLE-742: -- Summary: check applications when remove site (was: disable streams when site has been removed) > check applications when remove site > --- > > Key: EAGLE-742 > URL: https://issues.apache.org/jira/browse/EAGLE-742 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > When site has been removed, streams defined are still there. We need remove > them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-742) disable streams when site has been removed
[ https://issues.apache.org/jira/browse/EAGLE-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu updated EAGLE-742: -- Summary: disable streams when site has been removed (was: delete streams when site has been removed) > disable streams when site has been removed > -- > > Key: EAGLE-742 > URL: https://issues.apache.org/jira/browse/EAGLE-742 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > When site has been removed, streams defined are still there. We need remove > them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-742) delete streams when site has been removed
wujinhu created EAGLE-742: - Summary: delete streams when site has been removed Key: EAGLE-742 URL: https://issues.apache.org/jira/browse/EAGLE-742 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 When site has been removed, streams defined are still there. We need remove them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #612: EAGLE-728 Application can't load applicat...
Github user wujinhu commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/612#discussion_r86710130
--- Diff:
eagle-jpm/eagle-hadoop-queue/src/main/resources/META-INF/providers/org.apache.eagle.hadoop.queue.HadoopQueueRunningAppProvider.xml
---
@@ -47,6 +47,12 @@
interval seconds of fetching metric from resource
manager
10
+
+ job.name.normalization.rules.key
+ Job Name Normalization Rules Key
+ User use -Dkey=job name normalization
rules
+ ^(.*)[0-9]{4}/[0-9]{2}/[0-9]{2}/[0-9]{2}$ => $1~ ;
^(oozie:launcher):T=(.*):W=(.*):A=(.*):ID=(?:.*)$ => $1-$2-$3-$4~ ;
^(.*)([0-9]{10})$ => $1~ ;
^[0-9a-z]{8}-[0-9a-z]{4}-[0-9a-z]{4}-[0-9a-z]{4}-[0-9a-z]{12}$ => uuid~ ;
^(.*)(?:[0-9]{8}/[0-9]{2}_[0-9]{2})$ => $1~
+
--- End diff --
Please remove this configuration from these Provider xml files. Since we
have 'Custom' function so that advanced users can add other configurations(like
this) if they want.
If user passes this custom defined configuration, it will override the
predefined value.
---
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 #612: EAGLE-728 Application can't load applicat...
Github user wujinhu commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/612#discussion_r86709972
--- Diff:
eagle-jpm/eagle-jpm-util/src/main/java/org/apache/eagle/jpm/util/JobNameNormalization.java
---
@@ -64,7 +67,7 @@ private JobNameNormalization() {
// load normalization rules
Config conf = ConfigFactory.load();
--- End diff --
Please remove this line(Config conf = ConfigFactory.load();) from code.
Since our application is a storm topology, it will be better if we pass
configure to it when we initialize it so that it won't load dynamically.
Please do a simple refactor and just pass Config object to this class.
---
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 #602: EAGLE-728 Application can't load application.pro...
Github user wujinhu commented on the issue: https://github.com/apache/incubator-eagle/pull/602 Please close this, I see another PR has been opened for the same issue. --- 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 #604: Eagle-725 Update timeSrv logic & policy detail
Github user wujinhu commented on the issue: https://github.com/apache/incubator-eagle/pull/604 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. ---
[GitHub] incubator-eagle pull request #603: EAGLE-729:add hbase kerberose principle a...
Github user wujinhu commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/603#discussion_r86303727
--- Diff:
eagle-topology-check/eagle-topology-app/src/main/resources/META-INF/providers/org.apache.eagle.topology.TopologyCheckAppProvider.xml
---
@@ -88,14 +88,20 @@
Hbase Master Principal
hadoop/_h...@example.com
-
+
-dataSourceConfig.hbase.kerberos.master.principal
-Hbase Master Principal
+dataSourceConfig.hbase.kerberos.eagle.principal
--- End diff --
Does it work? I see the code
hBaseConfig.hbaseMasterPrincipal =
config.getString("dataSourceConfig.hbase.kerberos.master.principal");
if (hBaseConfig.eaglePrincipal != null && hBaseConfig.eagleKeytab != null
&& !hBaseConfig.eaglePrincipal.isEmpty() &&
!hBaseConfig.eagleKeytab.isEmpty()) {
this.kerberosEnable = true;
this.hBaseConfiguration.set("hbase.security.authentication",
"kerberos");
this.hBaseConfiguration.set("hbase.master.kerberos.principal",
hBaseConfig.hbaseMasterPrincipal);
}
---
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 #602: EAGLE-728 Application can't load application.pro...
Github user wujinhu commented on the issue: https://github.com/apache/incubator-eagle/pull/602 Reviewed. We should not add application specific level configuration to eagle server configuration. I think we can hard code, and override it if user passes this configuration from web ui. --- 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 #598: [EAGLE-719] fix configuration bug in application...
Github user wujinhu commented on the issue: https://github.com/apache/incubator-eagle/pull/598 LGTM, @qingwen220 pls help check --- 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 #570: EAGLE-690 : integrage topology health che...
Github user wujinhu commented on a diff in the pull request: https://github.com/apache/incubator-eagle/pull/570#discussion_r86078128 --- Diff: eagle-topology-check/eagle-topology-app/src/main/resources/META-INF/providers/org.apache.eagle.topology.TopologyCheckAppProvider.xml --- @@ -89,28 +97,36 @@ Hbase Master Principal hadoop/_h...@example.com - + + +dataSourceConfig.hbase.kerberos.eagle.principal +hbaseEaglePrincipal +Hbase eagle Principal + + --- End diff -- Other config like eagle service should read config through execute(Config config, StormEnvironment environment) call. --- 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 #570: EAGLE-690 : integrage topology health che...
Github user wujinhu commented on a diff in the pull request:
https://github.com/apache/incubator-eagle/pull/570#discussion_r86077566
--- Diff:
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/storm/HealthCheckParseBolt.java
---
@@ -0,0 +1,84 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+package org.apache.eagle.topology.storm;
+
+import backtype.storm.task.OutputCollector;
+import backtype.storm.task.TopologyContext;
+import backtype.storm.topology.OutputFieldsDeclarer;
+import backtype.storm.topology.base.BaseRichBolt;
+import backtype.storm.tuple.Fields;
+import backtype.storm.tuple.Tuple;
+
+import com.fasterxml.jackson.databind.ObjectMapper;
+
+import org.apache.eagle.topology.TopologyConstants;
+import org.apache.eagle.topology.entity.HealthCheckParseAPIEntity;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import storm.kafka.bolt.mapper.FieldNameBasedTupleToKafkaMapper;
+
+import java.util.Arrays;
+import java.util.Map;
+import java.util.TreeMap;
+
+/**
+ * Since 10/26/16.
+ */
+public class HealthCheckParseBolt extends BaseRichBolt {
+/**
+*
+*/
+ private static final long serialVersionUID = 1L;
--- End diff --
Please follow code style
---
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-715) optimize some configurations for alert
[ https://issues.apache.org/jira/browse/EAGLE-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-715. - Resolution: Fixed > optimize some configurations for alert > -- > > Key: EAGLE-715 > URL: https://issues.apache.org/jira/browse/EAGLE-715 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > optimize some configurations for alert -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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] [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] [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)
[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 <wujinhu...@126.com> 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] [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)
[jira] [Closed] (EAGLE-700) API /policies/{policyId} throws exception if policy does not exist
[
https://issues.apache.org/jira/browse/EAGLE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wujinhu closed EAGLE-700.
-
Resolution: Fixed
> API /policies/{policyId} throws exception if policy does not exist
> --
>
> Key: EAGLE-700
> URL: https://issues.apache.org/jira/browse/EAGLE-700
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
> Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> API /policies/{policyId} throws exception if policy does not exist
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-eagle pull request #579: [EAGLE-700] API /policies/{policyId} thro...
GitHub user wujinhu opened a pull request:
https://github.com/apache/incubator-eagle/pull/579
[EAGLE-700] API /policies/{policyId} throws exception if policy does not
exist
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wujinhu/incubator-eagle EAGLE-693
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/579.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 #579
commit 6f66d6606f3e92d20ffc41e909ceab7d52b0c676
Author: wujinhu <wujinhu...@126.com>
Date: 2016-10-28T07:51:37Z
API /policies/{policyId} throws exception if policy does not exist
---
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-700) API /policies/{policyId} throws exception if policy does not exist
wujinhu created EAGLE-700:
-
Summary: API /policies/{policyId} throws exception if policy does
not exist
Key: EAGLE-700
URL: https://issues.apache.org/jira/browse/EAGLE-700
Project: Eagle
Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
Fix For: v0.5.0
API /policies/{policyId} throws exception if policy does not exist
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-eagle pull request #577: [EAGLE-694] alert engine could not reduce...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/577 [EAGLE-694] alert engine could not reduce alert bolt number when parallelism of p⦠You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-694 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/577.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 #577 commit a229476b99555d6ec0951e3af69e7b0f1e02eac7 Author: wujinhu <wujinhu...@126.com> Date: 2016-10-28T06:07:26Z alert engine could not reduce alert bolt number when parallelism of policy reduces --- 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 #580: [EAGLE-693] fix application could not det...
GitHub user wujinhu reopened a pull request: https://github.com/apache/incubator-eagle/pull/580 [EAGLE-693] fix application could not detect stream change You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-700 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/580.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 #580 commit 4a32d92193ad5f48fb0dd9f59ac2070b55ad9c62 Author: wujinhu <wujinhu...@126.com> Date: 2016-10-28T09:25:16Z fix application could not detect stream change --- 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 #580: [EAGLE-693] fix application could not det...
Github user wujinhu closed the pull request at: https://github.com/apache/incubator-eagle/pull/580 --- 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 #578: [EAGLE-697] fix wrong url-concatenation for moni...
Github user wujinhu commented on the issue: https://github.com/apache/incubator-eagle/pull/578 Reviewed, pls merge --- 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-694) alert engine could not reduce alert bolt number when parallelism of policy reduces
[ https://issues.apache.org/jira/browse/EAGLE-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-694. - Resolution: Fixed > alert engine could not reduce alert bolt number when parallelism of policy > reduces > -- > > Key: EAGLE-694 > URL: https://issues.apache.org/jira/browse/EAGLE-694 > Project: Eagle > Issue Type: Bug > Reporter: wujinhu >Assignee: wujinhu > > alert engine could not reduce alert bolt number when parallelism of policy > reduces -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #574: [Eagle 695] fetching hadoop.cluster.allocatedvir...
Github user wujinhu commented on the issue: https://github.com/apache/incubator-eagle/pull/574 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-694) alert engine could not reduce alert bolt number when parallelism of policy reduces
wujinhu created EAGLE-694: - Summary: alert engine could not reduce alert bolt number when parallelism of policy reduces Key: EAGLE-694 URL: https://issues.apache.org/jira/browse/EAGLE-694 Project: Eagle Issue Type: Bug Reporter: wujinhu Assignee: wujinhu alert engine could not reduce alert bolt number when parallelism of policy reduces -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-659) MR history feeder and Alert Engine integration
[ https://issues.apache.org/jira/browse/EAGLE-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-659. - Resolution: Resolved > MR history feeder and Alert Engine integration > -- > > Key: EAGLE-659 > URL: https://issues.apache.org/jira/browse/EAGLE-659 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > When JPM finds fail jobs, it will send data to kafka which will read by alert > engine and generates alerts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-659) MR history feeder and Alert Engine integraton
[ https://issues.apache.org/jira/browse/EAGLE-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu updated EAGLE-659: -- Summary: MR history feeder and Alert Engine integraton (was: Eagle JPM send fail job alerts by Alert Engine) > MR history feeder and Alert Engine integraton > - > > Key: EAGLE-659 > URL: https://issues.apache.org/jira/browse/EAGLE-659 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > When JPM finds fail jobs, it will send data to kafka which will read by alert > engine and generates alerts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-659) MR history feeder and Alert Engine integration
[ https://issues.apache.org/jira/browse/EAGLE-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu updated EAGLE-659: -- Summary: MR history feeder and Alert Engine integration (was: MR history feeder and Alert Engine integraton) > MR history feeder and Alert Engine integration > -- > > Key: EAGLE-659 > URL: https://issues.apache.org/jira/browse/EAGLE-659 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > When JPM finds fail jobs, it will send data to kafka which will read by alert > engine and generates alerts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-682) fix /policies/{policyId}/publishments bug
[
https://issues.apache.org/jira/browse/EAGLE-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wujinhu closed EAGLE-682.
-
Resolution: Fixed
> fix /policies/{policyId}/publishments bug
> -
>
> Key: EAGLE-682
> URL: https://issues.apache.org/jira/browse/EAGLE-682
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
> Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> fix null policy id exception
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (EAGLE-679) Fix missing CoprocessorService and MR Running feeder task number limitation
[ https://issues.apache.org/jira/browse/EAGLE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-679. - Resolution: Fixed > Fix missing CoprocessorService and MR Running feeder task number limitation > --- > > Key: EAGLE-679 > URL: https://issues.apache.org/jira/browse/EAGLE-679 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > 1. fix missing CoprocessorService > ERROR [2016-10-25 02:56:34,495] net.sf.extcos.internal.JavaResourceAccessor: > Unable to read interface > [org.apache.hadoop.hbase.coprocessor.CoprocessorService] > ! java.io.IOException: Class not found > 2. If task number of a job greater than 5000, then does not fetch task details -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #560: [EAGLE-682] fix /policies/{policyId}/publ...
GitHub user wujinhu opened a pull request:
https://github.com/apache/incubator-eagle/pull/560
[EAGLE-682] fix /policies/{policyId}/publishments bug
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wujinhu/incubator-eagle EAGLE-682
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/560.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 #560
commit 94d24265b1ba371312700b366aef8d4a2e211e1e
Author: wujinhu <wujinhu...@126.com>
Date: 2016-10-25T09:03:03Z
fix /policies/{policyId}/publishments bug
---
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-682) fix /policies/{policyId}/publishments bug
wujinhu created EAGLE-682:
-
Summary: fix /policies/{policyId}/publishments bug
Key: EAGLE-682
URL: https://issues.apache.org/jira/browse/EAGLE-682
Project: Eagle
Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
Fix For: v0.5.0
fix null policy id exception
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-eagle pull request #558: [EAGLE-679] Fix missing CoprocessorServic...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/558 [EAGLE-679] Fix missing CoprocessorService and MR Running feeder task number limi⦠You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-679 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/558.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 #558 commit e8504f369457d6cc301009b61545f294b8cbbf4e Author: wujinhu <wujinhu...@126.com> Date: 2016-10-25T03:22:45Z Fix missing CoprocessorService and MR Running feeder task number limitation --- 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-679) Fix missing CoprocessorService and MR Running feeder task number limitation
wujinhu created EAGLE-679: - Summary: Fix missing CoprocessorService and MR Running feeder task number limitation Key: EAGLE-679 URL: https://issues.apache.org/jira/browse/EAGLE-679 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 1. fix missing CoprocessorService ERROR [2016-10-25 02:56:34,495] net.sf.extcos.internal.JavaResourceAccessor: Unable to read interface [org.apache.hadoop.hbase.coprocessor.CoprocessorService] ! java.io.IOException: Class not found 2. If task number of a job greater than 5000, then does not fetch task details -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-674) fix grouping between AlertBolt and AlertPublisher
[ https://issues.apache.org/jira/browse/EAGLE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-674. - Resolution: Fixed > fix grouping between AlertBolt and AlertPublisher > - > > Key: EAGLE-674 > URL: https://issues.apache.org/jira/browse/EAGLE-674 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > Currently, it is fields grouping > boltDeclarer.fieldsGrouping(alertBoltNamePrefix + i, new > Fields(AlertConstants.FIELD_0)); > Sometimes, traffic will go to only one task of alert publisher, we should > change to shuffleGrouping -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #557: [EAGLE-674] fix grouping between AlertBol...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/557 [EAGLE-674] fix grouping between AlertBolt and AlertPublisher 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/557.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 #557 commit c82fe370ef20db5437f072bf25ec90f4f2917bba Author: wujinhu <wujinhu...@126.com> Date: 2016-10-24T05:54:02Z add numOfPublishExecutors to alert engine topology commit d25bfae642115560ccfc87218c168b52aa389d92 Author: wujinhu <wujinhu...@126.com> Date: 2016-10-24T08:44:34Z fix alertPublish grouping bug --- 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-674) fix grouping between AlertBolt and AlertPublisher
wujinhu created EAGLE-674: - Summary: fix grouping between AlertBolt and AlertPublisher Key: EAGLE-674 URL: https://issues.apache.org/jira/browse/EAGLE-674 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 Currently, it is fields grouping boltDeclarer.fieldsGrouping(alertBoltNamePrefix + i, new Fields(AlertConstants.FIELD_0)); Sometimes, traffic will go to only one task of alert publisher, we should change to shuffleGrouping -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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 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 <wujinhu...@126.com> 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 created EAGLE-673: - Summary: add numOfPublishBolts to alert engine topology Key: EAGLE-673 URL: https://issues.apache.org/jira/browse/EAGLE-673 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 When creates alert engine topology BoltDeclarer boltDeclarer = builder.setBolt(alertPublishBoltName, publisherBolt).setNumTasks(numOfPublishTasks); builder does not set number of publish bolts which will cause these tasks are in only one bolt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-146) SiddhiExtensionLoader Error: viewing zip file for jar:./lib/ojdbc6.jar
[
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<String, Class> 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.s
[jira] [Closed] (EAGLE-655) Fix metadata bug
[ https://issues.apache.org/jira/browse/EAGLE-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-655. - Resolution: Fixed > Fix metadata bug > > > Key: EAGLE-655 > URL: https://issues.apache.org/jira/browse/EAGLE-655 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > fix metadata bug, context saved to metastore -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-653) remove zk root from configure
[ https://issues.apache.org/jira/browse/EAGLE-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-653. - Resolution: Resolved > remove zk root from configure > - > > Key: EAGLE-653 > URL: https://issues.apache.org/jira/browse/EAGLE-653 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > add applicationListener to MR feeders so that they can check some > environments like connection... before they start -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-653) remove zk root from configure
[ https://issues.apache.org/jira/browse/EAGLE-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu updated EAGLE-653: -- Summary: remove zk root from configure (was: Add ApplicationListener To MR Feeders) > remove zk root from configure > - > > Key: EAGLE-653 > URL: https://issues.apache.org/jira/browse/EAGLE-653 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > add applicationListener to MR feeders so that they can check some > environments like connection... before they start -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #542: [EAGLE-653] remove zk root from configure
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/542 [EAGLE-653] remove zk root from configure You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-653 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/542.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 #542 commit 19824483bf41dc5e6bd3f7308b25f771ea64805d Author: wujinhu <wujinhu...@126.com> Date: 2016-10-20T10:31:36Z remove zk root from configure --- 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-653) Add ApplicationListener To MR Feeders
wujinhu created EAGLE-653: - Summary: Add ApplicationListener To MR Feeders Key: EAGLE-653 URL: https://issues.apache.org/jira/browse/EAGLE-653 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 add applicationListener to MR feeders so that they can check some environments like connection... before they start -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #537: [EAGLE-642] move application runtime conf...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/537 [EAGLE-642] move application runtime configure to ApplicationEntity context You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-644 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/537.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 #537 commit 7e6dc2edbfb678cc39be51290d4585e4e43f2a37 Author: wujinhu <wujinhu...@126.com> Date: 2016-10-20T06:36:07Z move application runtime configure to ApplicationEntity context --- 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-644) optimize some default configurations for JPM
[ https://issues.apache.org/jira/browse/EAGLE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-644. - Resolution: Resolved > optimize some default configurations for JPM > > > Key: EAGLE-644 > URL: https://issues.apache.org/jira/browse/EAGLE-644 > Project: Eagle > Issue Type: Improvement > Reporter: wujinhu > Assignee: wujinhu > > optimize some default configurations for JPM -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-644) optimize some default configurations for JPM
wujinhu created EAGLE-644: - Summary: optimize some default configurations for JPM Key: EAGLE-644 URL: https://issues.apache.org/jira/browse/EAGLE-644 Project: Eagle Issue Type: Improvement Reporter: wujinhu Assignee: wujinhu optimize some default configurations for JPM -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #535: [EAGLE-644] optimize some default configu...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/535 [EAGLE-644] optimize some default configurations for JPM You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-642 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/535.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 #535 commit 75c753a6449340a32ed8bc32fa02156a7585f573 Author: wujinhu <wujinhu...@126.com> Date: 2016-10-20T02:24:44Z optimize some default configurations for JPM --- 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-642) move application runtime configure to ApplicationEntity context
wujinhu created EAGLE-642: - Summary: move application runtime configure to ApplicationEntity context Key: EAGLE-642 URL: https://issues.apache.org/jira/browse/EAGLE-642 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 When install an application, there are some configures like appId/siteId that should not changed by user, so we move them to context. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-43) Eagle Job Running Spout should support HTTPS
[ https://issues.apache.org/jira/browse/EAGLE-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-43. Resolution: Fixed Fix Version/s: v0.5.0 > Eagle Job Running Spout should support HTTPS > > > Key: EAGLE-43 > URL: https://issues.apache.org/jira/browse/EAGLE-43 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.3.0 >Reporter: Libin, Sun >Assignee: wujinhu > Fix For: v0.5.0 > > > Job Running Spout is a data source for hive security monitoring, it get data > from RM yarn API and RM web page, currently we only support HTTP, should add > HTTPS supprot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-638) clean up configuration for Eagle JPM aggregation feeder
[ https://issues.apache.org/jira/browse/EAGLE-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-638. - Resolution: Resolved > clean up configuration for Eagle JPM aggregation feeder > --- > > Key: EAGLE-638 > URL: https://issues.apache.org/jira/browse/EAGLE-638 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > 1. remove useless configure > 2. add required field to application provider.xml > 3. add description to application provider.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #533: [EAGLE-638] clean up configuration for Ea...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/533 [EAGLE-638] clean up configuration for Eagle JPM aggregation feeder You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-638 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/533.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 #533 commit 8c08cd15e029f9e629615b5f991a83d31d7dec06 Author: wujinhu <wujinhu...@126.com> Date: 2016-10-19T07:30:57Z clean up configuration for Eagle JPM aggregation feeder --- 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-638) clean up configuration for Eagle JPM aggregation feeder
wujinhu created EAGLE-638: - Summary: clean up configuration for Eagle JPM aggregation feeder Key: EAGLE-638 URL: https://issues.apache.org/jira/browse/EAGLE-638 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 1. remove useless configure 2. add required field to application provider.xml 3. add description to application provider.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-558) Use dynamical loaded jarPath as default value in ApplicationEntity
[ https://issues.apache.org/jira/browse/EAGLE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-558. - Resolution: Resolved > Use dynamical loaded jarPath as default value in ApplicationEntity > -- > > Key: EAGLE-558 > URL: https://issues.apache.org/jira/browse/EAGLE-558 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: wujinhu > Fix For: v0.5.0 > > > Use dynamical loaded jarPath as default value in ApplicationEntity, which > could also be forcefully replaced with InstallOperation > It's an improvement from patch: > https://github.com/apache/incubator-eagle/commit/6fc103338fa3e3275a1357144dfab2feb1a103ec#diff-c9c5f683c463429e5e1c01b8b6fa71b7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-634) clean up configuration for MR running feeder
[ https://issues.apache.org/jira/browse/EAGLE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu closed EAGLE-634. - Resolution: Resolved > clean up configuration for MR running feeder > > > Key: EAGLE-634 > URL: https://issues.apache.org/jira/browse/EAGLE-634 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > 1. remove useless configure > 2. add required field to application provider.xml > 3. add description to application provider.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #530: [EAGLE-634] clean up configuration for MR...
GitHub user wujinhu opened a pull request: https://github.com/apache/incubator-eagle/pull/530 [EAGLE-634] clean up configuration for MR running feeder You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/incubator-eagle EAGLE-634 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/530.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 #530 commit 317b869935e84a37f0ee7e9f7bed9e6df64724de Author: wujinhu <wujinhu...@126.com> Date: 2016-10-19T02:45:59Z clean up configuration for MR running feeder --- 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 #527: Minor: set task number of UnitTopologyRunner
Github user wujinhu commented on the issue: https://github.com/apache/incubator-eagle/pull/527 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] [Updated] (EAGLE-634) clean up configuration for MR running feeder
[ https://issues.apache.org/jira/browse/EAGLE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujinhu updated EAGLE-634: -- Description: 1. remove useless configure 2. add required field to application provider.xml 3. add description to application provider.xml > clean up configuration for MR running feeder > > > Key: EAGLE-634 > URL: https://issues.apache.org/jira/browse/EAGLE-634 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 > Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > 1. remove useless configure > 2. add required field to application provider.xml > 3. add description to application provider.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-634) clean up configuration for MR running feeder
wujinhu created EAGLE-634: - Summary: clean up configuration for MR running feeder Key: EAGLE-634 URL: https://issues.apache.org/jira/browse/EAGLE-634 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
