[jira] [Created] (EAGLE-577) UI policy management
Jilin, Jiang created EAGLE-577: -- Summary: UI policy management Key: EAGLE-577 URL: https://issues.apache.org/jira/browse/EAGLE-577 Project: Eagle Issue Type: Task Affects Versions: 0.5 Reporter: Jilin, Jiang Assignee: Jilin, Jiang Fix For: 0.5 For 0.5 api, policy management api has been update. UI also need fit for that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-574) UI refactor for support 0.5 api
[ https://issues.apache.org/jira/browse/EAGLE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jilin, Jiang resolved EAGLE-574. Resolution: Fixed > UI refactor for support 0.5 api > --- > > Key: EAGLE-574 > URL: https://issues.apache.org/jira/browse/EAGLE-574 > Project: Eagle > Issue Type: Task >Affects Versions: 0.5 >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > Labels: eagle-frontend, eagle-jpm-web, eagle-ui, > eagle-ui-framework > Fix For: 0.5 > > > Eagle 0.5 updates the rest api interface and UI need also update for support > the api. > * Remove feature > * Support app provider > * Create JPM UI application > * Redesign site logic > * Widget support -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #462: EAGLE-576: dedup enhancements
GitHub user garrettlish opened a pull request: https://github.com/apache/incubator-eagle/pull/462 EAGLE-576: dedup enhancements 1. per publishment per cache, without global cache 2. support dedup without state field 3. emit raw alert into configured namespace 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/462.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 #462 commit eb26286126c34272967d1159d07b0d645157c61a Author: Xiancheng Li Date: 2016-09-28T00:54:43Z EAGLE-576: dedup enhancements 1. per publishment per cache, without global cache 2. support dedup without state field 3. emit raw alert into configured namespace --- 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-576) Dedup enhancements
[ https://issues.apache.org/jira/browse/EAGLE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528594#comment-15528594 ] ASF GitHub Bot commented on EAGLE-576: -- GitHub user garrettlish opened a pull request: https://github.com/apache/incubator-eagle/pull/462 EAGLE-576: dedup enhancements 1. per publishment per cache, without global cache 2. support dedup without state field 3. emit raw alert into configured namespace 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/462.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 #462 commit eb26286126c34272967d1159d07b0d645157c61a Author: Xiancheng Li Date: 2016-09-28T00:54:43Z EAGLE-576: dedup enhancements 1. per publishment per cache, without global cache 2. support dedup without state field 3. emit raw alert into configured namespace > Dedup enhancements > -- > > Key: EAGLE-576 > URL: https://issues.apache.org/jira/browse/EAGLE-576 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > 1. per publishment per cache, without global cache > 2. support dedup without state field > 3. emit raw alert into configured namespace -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-432) Application status monitoring
[ https://issues.apache.org/jira/browse/EAGLE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528587#comment-15528587 ] ASF GitHub Bot commented on EAGLE-432: -- GitHub user DadanielZ opened a pull request: https://github.com/apache/incubator-eagle/pull/461 [EAGLE-432] Application status monitoring Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- - REST API call of app status can return: "INITIALIZED" "STARTING" "RUNNING" "STOPPING" - Added CheckStatus Operation as a new application Operation - ApplicationStatusUpdateService will probe topology status periodically and update the status in application Entity, this background task is based on "guava". The initial delay and period setting can be set in configuration file. - status() in StormExecutionRuntime supports both "LOCAL" and "CLUSTER" You can merge this pull request into a Git repository by running: $ git pull https://github.com/DadanielZ/incubator-eagle EAGLE-432-Application-status-monitoring Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/461.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 #461 commit ab0c583b9fee6b3d7d9ad5200dcb0f360f79e060 Author: DadanielZ Date: 2016-09-28T06:24:03Z [EAGLE-432] Application status monitoring - REST API call of app status can return: "INITIALIZED" "STARTING" "RUNNING" "STOPPING" - Added CheckStatus Operation as a new application Operation - ApplicationStatusUpdateService will probe topology status periodically and update the status in application Entity, this background task is based on "guava". The initial delay and period setting can be set in configuration file. - status() in StormExecutionRuntime supports both "LOCAL" and "CLUSTER" > Application status monitoring > - > > Key: EAGLE-432 > URL: https://issues.apache.org/jira/browse/EAGLE-432 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Edward Zhang >Assignee: DanielZhou > Fix For: v0.5.0 > > > App framework needs to probe application status periodically or on demand. > ApplicationEntity contains status field, and this field's value should come > from physical storm applications. > We can start background threads to check application status or on-demand. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #461: [EAGLE-432] Application status monitoring
GitHub user DadanielZ opened a pull request: https://github.com/apache/incubator-eagle/pull/461 [EAGLE-432] Application status monitoring Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- - REST API call of app status can return: "INITIALIZED" "STARTING" "RUNNING" "STOPPING" - Added CheckStatus Operation as a new application Operation - ApplicationStatusUpdateService will probe topology status periodically and update the status in application Entity, this background task is based on "guava". The initial delay and period setting can be set in configuration file. - status() in StormExecutionRuntime supports both "LOCAL" and "CLUSTER" You can merge this pull request into a Git repository by running: $ git pull https://github.com/DadanielZ/incubator-eagle EAGLE-432-Application-status-monitoring Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/461.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 #461 commit ab0c583b9fee6b3d7d9ad5200dcb0f360f79e060 Author: DadanielZ Date: 2016-09-28T06:24:03Z [EAGLE-432] Application status monitoring - REST API call of app status can return: "INITIALIZED" "STARTING" "RUNNING" "STOPPING" - Added CheckStatus Operation as a new application Operation - ApplicationStatusUpdateService will probe topology status periodically and update the status in application Entity, this background task is based on "guava". The initial delay and period setting can be set in configuration file. - status() in StormExecutionRuntime supports both "LOCAL" and "CLUSTER" --- 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-576) Dedup enhancements
[ https://issues.apache.org/jira/browse/EAGLE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garrett Li updated EAGLE-576: - Description: 1. per publishment per cache, without global cache 2. support dedup without state field 3. emit raw alert into configured namespace was: 1. per publishment per cache, without global cache 2. support dedup without state field > Dedup enhancements > -- > > Key: EAGLE-576 > URL: https://issues.apache.org/jira/browse/EAGLE-576 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > 1. per publishment per cache, without global cache > 2. support dedup without state field > 3. emit raw alert into configured namespace -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-576) Dedup enhancements
Garrett Li created EAGLE-576: Summary: Dedup enhancements Key: EAGLE-576 URL: https://issues.apache.org/jira/browse/EAGLE-576 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Garrett Li Assignee: Garrett Li Fix For: v0.5.0 1. per publishment per cache, without global cache 2. support dedup without state field -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EAGLE-566) add dedup fields into publishment compare consideration
[ https://issues.apache.org/jira/browse/EAGLE-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garrett Li closed EAGLE-566. Resolution: Fixed > add dedup fields into publishment compare consideration > --- > > Key: EAGLE-566 > URL: https://issues.apache.org/jira/browse/EAGLE-566 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > add dedup fields into publishment compare consideration, without it, > publishment dedup fields change won't be reloaded -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-575) Refactor StaticWebApplication to StaticApplication to support both web/static application
[
https://issues.apache.org/jira/browse/EAGLE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-575:
---
Description:
* Format appId as EAGLE_$siteId_$appType in upper case for easily being
managed in storm ui
* Refactor StaticWebApplication to StaticApplication to support both web/static
application
* Fix test failure problem caused by calling application.run directly
was:
* Format appId as "EAGLE_{siteId}_{appType}" in upper case for easily being
managed in storm ui
* Refactor StaticWebApplication to StaticApplication to support both web/static
application
* Fix test failure problem caused by calling application.run directly
> Refactor StaticWebApplication to StaticApplication to support both web/static
> application
> -
>
> Key: EAGLE-575
> URL: https://issues.apache.org/jira/browse/EAGLE-575
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Labels: eagle-app-framework
> Fix For: v0.5.0
>
>
> * Format appId as EAGLE_$siteId_$appType in upper case for easily being
> managed in storm ui
> * Refactor StaticWebApplication to StaticApplication to support both
> web/static application
> * Fix test failure problem caused by calling application.run directly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-575) Refactor StaticWebApplication to StaticApplication to support both web/static application
[
https://issues.apache.org/jira/browse/EAGLE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-575:
---
Description:
* Format appId as "EAGLE_{siteId}_{appType}" in upper case for easily being
managed in storm ui
* Refactor StaticWebApplication to StaticApplication to support both web/static
application
* Fix test failure problem caused by calling application.run directly
was:
* Format appId as "EAGLE_{siteId}_{appType}" in upper case for easily being
managed in storm ui
*
> Refactor StaticWebApplication to StaticApplication to support both web/static
> application
> -
>
> Key: EAGLE-575
> URL: https://issues.apache.org/jira/browse/EAGLE-575
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Labels: eagle-app-framework
> Fix For: v0.5.0
>
>
> * Format appId as "EAGLE_{siteId}_{appType}" in upper case for easily being
> managed in storm ui
> * Refactor StaticWebApplication to StaticApplication to support both
> web/static application
> * Fix test failure problem caused by calling application.run directly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-575) Refactor StaticWebApplication to StaticApplication to support both web/static application
[
https://issues.apache.org/jira/browse/EAGLE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-575:
---
Labels: eagle-app-framework (was: )
> Refactor StaticWebApplication to StaticApplication to support both web/static
> application
> -
>
> Key: EAGLE-575
> URL: https://issues.apache.org/jira/browse/EAGLE-575
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Labels: eagle-app-framework
> Fix For: v0.5.0
>
>
> * Format appId as "EAGLE_{siteId}_{appType}" in upper case for easily being
> managed in storm ui
> * Refactor StaticWebApplication to StaticApplication to support both
> web/static application
> * Fix test failure problem caused by calling application.run directly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EAGLE-575) Refactor StaticWebApplication to StaticApplication to support both web/static application
[
https://issues.apache.org/jira/browse/EAGLE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-575:
---
Description:
* Format appId as "EAGLE_{siteId}_{appType}" in upper case for easily being
managed in storm ui
*
> Refactor StaticWebApplication to StaticApplication to support both web/static
> application
> -
>
> Key: EAGLE-575
> URL: https://issues.apache.org/jira/browse/EAGLE-575
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> * Format appId as "EAGLE_{siteId}_{appType}" in upper case for easily being
> managed in storm ui
> *
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (EAGLE-575) Refactor StaticWebApplication to StaticApplication to support both web/static application
Hao Chen created EAGLE-575: -- Summary: Refactor StaticWebApplication to StaticApplication to support both web/static application Key: EAGLE-575 URL: https://issues.apache.org/jira/browse/EAGLE-575 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-574) UI refactor for support 0.5 api
[ https://issues.apache.org/jira/browse/EAGLE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528483#comment-15528483 ] ASF GitHub Bot commented on EAGLE-574: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/460 > UI refactor for support 0.5 api > --- > > Key: EAGLE-574 > URL: https://issues.apache.org/jira/browse/EAGLE-574 > Project: Eagle > Issue Type: Task >Affects Versions: 0.5 >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > Labels: eagle-frontend, eagle-jpm-web, eagle-ui, > eagle-ui-framework > Fix For: 0.5 > > > Eagle 0.5 updates the rest api interface and UI need also update for support > the api. > * Remove feature > * Support app provider > * Create JPM UI application > * Redesign site logic > * Widget support -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #460: EAGLE-574 UI refactor for support 0.5 api
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/460 --- 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-574) UI refactor for support 0.5 api
[ https://issues.apache.org/jira/browse/EAGLE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-574: --- Labels: eagle-frontend eagle-jpm-web eagle-ui eagle-ui-framework (was: ) > UI refactor for support 0.5 api > --- > > Key: EAGLE-574 > URL: https://issues.apache.org/jira/browse/EAGLE-574 > Project: Eagle > Issue Type: Task >Affects Versions: 0.5 >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > Labels: eagle-frontend, eagle-jpm-web, eagle-ui, > eagle-ui-framework > Fix For: 0.5 > > > Eagle 0.5 updates the rest api interface and UI need also update for support > the api. > * Remove feature > * Support app provider > * Create JPM UI application > * Redesign site logic > * Widget support -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-574) UI refactor for support 0.5 api
[ https://issues.apache.org/jira/browse/EAGLE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-574: --- Description: Eagle 0.5 updates the rest api interface and UI need also update for support the api. * Remove feature * Support app provider * Create JPM UI application * Redesign site logic * Widget support was:Eagle 0.5 updates the rest api interface and UI need also update for support the api. > UI refactor for support 0.5 api > --- > > Key: EAGLE-574 > URL: https://issues.apache.org/jira/browse/EAGLE-574 > Project: Eagle > Issue Type: Task >Affects Versions: 0.5 >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > Fix For: 0.5 > > > Eagle 0.5 updates the rest api interface and UI need also update for support > the api. > * Remove feature > * Support app provider > * Create JPM UI application > * Redesign site logic > * Widget support -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #460: EAGLE-574 UI refactor for support 0.5 api
GitHub user zombieJ opened a pull request: https://github.com/apache/incubator-eagle/pull/460 EAGLE-574 UI refactor for support 0.5 api Eagle 0.5 updates the rest api interface and UI need also update for support the api. * Remove feature * Support app provider * Create JPM UI application * Redesign site logic * Widget support You can merge this pull request into a Git repository by running: $ git pull https://github.com/zombieJ/incubator-eagle ui Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/460.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 #460 commit 7ca46b099f18d0c4d7cbfd12f175f9a45bfec349 Author: jiljiang Date: 2016-06-30T08:34:42Z 0.5 init commit 881a21052137bbd2e6d6d917baedda07035fde91 Author: jiljiang Date: 2016-07-01T07:18:04Z add alert page commit 14f5793f334d281d4a3b9b8c96cb46a782084b4b Author: jiljiang Date: 2016-07-01T08:21:03Z alert tab commit 3c9472f6c54a7b43b993b05730558640144dbd20 Author: jiljiang Date: 2016-07-04T05:23:50Z sortable commit 60ac69968f9a0b7ed97164558d766f8b73c3af39 Author: jiljiang Date: 2016-07-04T10:19:09Z policy list commit cb28ea5ffe003eaa1c6175f6dfcdc27d687ec321 Author: jiljiang Date: 2016-07-05T01:51:02Z create page commit b611dd32e79249e7dff87df61eba43c1fa135624 Author: jiljiang Date: 2016-07-06T10:14:48Z edit page commit 73a917006557b5a2773dae62baf19eb77e6584fe Author: jiljiang Date: 2016-07-29T09:07:59Z site service commit 8fbad51bc74622f86632867bd9a94a84939ebee8 Author: jiljiang Date: 2016-08-01T08:44:08Z create with then commit 7555c68c5b11c016169a24f268b28156b4f0fc2a Author: jiljiang Date: 2016-08-01T10:36:53Z install app commit 94c991b0fe9c939f2c038413c5c3d966d5eb107f Author: jiljiang Date: 2016-08-01T12:12:37Z application status class commit 9945f9abc495c00dc13d91e80ccc2ea6cc99fde5 Author: jiljiang Date: 2016-08-02T06:04:03Z site list add commit 2876529fc82a40b0d20f9e5a8cad81be371b7189 Author: jiljiang Date: 2016-08-02T07:08:17Z add streams list page commit f1d66704b644b015d7280b78deb95b2dcdf00bdc Author: jiljiang Date: 2016-08-02T07:51:52Z css adjust commit 3b2914ffcd1fb95b51421be4f41f717b6e1cb2d8 Author: jiljiang Date: 2016-08-02T08:35:58Z site nav class commit c12f08e47fa8c4cb7ed7dd671904965034af9773 Author: jiljiang Date: 2016-08-02T09:44:41Z site nav commit 678bc2fd1e15959af5d99d62295fd47800e5829e Author: jiljiang Date: 2016-08-03T04:53:44Z for moduling commit 5dba1235eca15fa9223874c101c5e544d079f7f8 Author: jiljiang Date: 2016-08-03T04:57:57Z do regiester commit cd8c1851952cdb55dcb596e1eea8708849b0a73d Author: jiljiang Date: 2016-08-03T06:42:48Z with regist commit 23f911babc8ddcfb68e077993d38a53f641feddf Author: jiljiang Date: 2016-08-03T11:10:16Z test plugin commit 2d60a037dbd8b5d3a4a1cf5023e9b4ae7edfde26 Author: jiljiang Date: 2016-08-04T05:43:22Z wrap deffered commit 2282ebfb2d01449c9c6d6c4e7e06ff109d3ca361 Author: jiljiang Date: 2016-08-04T06:37:12Z require module commit 9705c321b5c51bcc947f6d5aad6ebedab9503451 Author: jiljiang Date: 2016-08-05T10:11:09Z job list commit 8e79653bf6a1260f63c82d6068f8401550b8a7c3 Author: jiljiang Date: 2016-08-05T13:37:34Z list state commit edfad5e96a0c3c984df8b995fc4454bde9840fd9 Author: jiljiang Date: 2016-08-08T03:08:46Z enhance list commit d8c6b464d788b6f6443b6da2f72bd2713927d89a Author: jiljiang Date: 2016-08-09T06:49:03Z job detail commit 242a0dd9f344a5d3492f1313fbbfeb5f8d9dacab Author: jiljiang Date: 2016-08-16T08:23:51Z sort table opt commit 07102645043a6b46f770ca3bedf02d39a4d8632b Author: jiljiang Date: 2016-08-16T10:44:02Z node count commit d289016cdebac3cda246161d121651300a7d8256 Author: jiljiang Date: 2016-08-23T03:49:28Z dashboard compared task distribution commit 3f6339b2ed439022418309ea0a375318e63841f0 Author: jiljiang Date: 2016-08-23T10:19:38Z site promise logic 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-574) UI refactor for support 0.5 api
[ https://issues.apache.org/jira/browse/EAGLE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528323#comment-15528323 ] ASF GitHub Bot commented on EAGLE-574: -- GitHub user zombieJ opened a pull request: https://github.com/apache/incubator-eagle/pull/460 EAGLE-574 UI refactor for support 0.5 api Eagle 0.5 updates the rest api interface and UI need also update for support the api. * Remove feature * Support app provider * Create JPM UI application * Redesign site logic * Widget support You can merge this pull request into a Git repository by running: $ git pull https://github.com/zombieJ/incubator-eagle ui Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/460.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 #460 commit 7ca46b099f18d0c4d7cbfd12f175f9a45bfec349 Author: jiljiang Date: 2016-06-30T08:34:42Z 0.5 init commit 881a21052137bbd2e6d6d917baedda07035fde91 Author: jiljiang Date: 2016-07-01T07:18:04Z add alert page commit 14f5793f334d281d4a3b9b8c96cb46a782084b4b Author: jiljiang Date: 2016-07-01T08:21:03Z alert tab commit 3c9472f6c54a7b43b993b05730558640144dbd20 Author: jiljiang Date: 2016-07-04T05:23:50Z sortable commit 60ac69968f9a0b7ed97164558d766f8b73c3af39 Author: jiljiang Date: 2016-07-04T10:19:09Z policy list commit cb28ea5ffe003eaa1c6175f6dfcdc27d687ec321 Author: jiljiang Date: 2016-07-05T01:51:02Z create page commit b611dd32e79249e7dff87df61eba43c1fa135624 Author: jiljiang Date: 2016-07-06T10:14:48Z edit page commit 73a917006557b5a2773dae62baf19eb77e6584fe Author: jiljiang Date: 2016-07-29T09:07:59Z site service commit 8fbad51bc74622f86632867bd9a94a84939ebee8 Author: jiljiang Date: 2016-08-01T08:44:08Z create with then commit 7555c68c5b11c016169a24f268b28156b4f0fc2a Author: jiljiang Date: 2016-08-01T10:36:53Z install app commit 94c991b0fe9c939f2c038413c5c3d966d5eb107f Author: jiljiang Date: 2016-08-01T12:12:37Z application status class commit 9945f9abc495c00dc13d91e80ccc2ea6cc99fde5 Author: jiljiang Date: 2016-08-02T06:04:03Z site list add commit 2876529fc82a40b0d20f9e5a8cad81be371b7189 Author: jiljiang Date: 2016-08-02T07:08:17Z add streams list page commit f1d66704b644b015d7280b78deb95b2dcdf00bdc Author: jiljiang Date: 2016-08-02T07:51:52Z css adjust commit 3b2914ffcd1fb95b51421be4f41f717b6e1cb2d8 Author: jiljiang Date: 2016-08-02T08:35:58Z site nav class commit c12f08e47fa8c4cb7ed7dd671904965034af9773 Author: jiljiang Date: 2016-08-02T09:44:41Z site nav commit 678bc2fd1e15959af5d99d62295fd47800e5829e Author: jiljiang Date: 2016-08-03T04:53:44Z for moduling commit 5dba1235eca15fa9223874c101c5e544d079f7f8 Author: jiljiang Date: 2016-08-03T04:57:57Z do regiester commit cd8c1851952cdb55dcb596e1eea8708849b0a73d Author: jiljiang Date: 2016-08-03T06:42:48Z with regist commit 23f911babc8ddcfb68e077993d38a53f641feddf Author: jiljiang Date: 2016-08-03T11:10:16Z test plugin commit 2d60a037dbd8b5d3a4a1cf5023e9b4ae7edfde26 Author: jiljiang Date: 2016-08-04T05:43:22Z wrap deffered commit 2282ebfb2d01449c9c6d6c4e7e06ff109d3ca361 Author: jiljiang Date: 2016-08-04T06:37:12Z require module commit 9705c321b5c51bcc947f6d5aad6ebedab9503451 Author: jiljiang Date: 2016-08-05T10:11:09Z job list commit 8e79653bf6a1260f63c82d6068f8401550b8a7c3 Author: jiljiang Date: 2016-08-05T13:37:34Z list state commit edfad5e96a0c3c984df8b995fc4454bde9840fd9 Author: jiljiang Date: 2016-08-08T03:08:46Z enhance list commit d8c6b464d788b6f6443b6da2f72bd2713927d89a Author: jiljiang Date: 2016-08-09T06:49:03Z job detail commit 242a0dd9f344a5d3492f1313fbbfeb5f8d9dacab Author: jiljiang Date: 2016-08-16T08:23:51Z sort table opt commit 07102645043a6b46f770ca3bedf02d39a4d8632b Author: jiljiang Date: 2016-08-16T10:44:02Z node count commit d289016cdebac3cda246161d121651300a7d8256 Author: jiljiang Date: 2016-08-23T03:49:28Z dashboard compared task distribution commit 3f6339b2ed439022418309ea0a375318e63841f0 Author: jiljiang Date: 2016-08-23T10:19:38Z site promise logic update > UI refactor for support 0.5 api > --- > > Key: EAGLE-574 > URL: https://issues.apache.org/jira/browse/EAGLE-574 > Project: Eagle > Issue Type: Task >Affects Versions: 0.5 >Reporter: Jilin, Jiang >Assignee: Jilin, Jiang > Fix For: 0.5 > > > Eagle 0.5 updates the rest api interface and UI need also update for support > the api. -- This message was sent by Atlassian J
[jira] [Created] (EAGLE-574) UI refactor for support 0.5 api
Jilin, Jiang created EAGLE-574: -- Summary: UI refactor for support 0.5 api Key: EAGLE-574 URL: https://issues.apache.org/jira/browse/EAGLE-574 Project: Eagle Issue Type: Task Affects Versions: 0.5 Reporter: Jilin, Jiang Assignee: Jilin, Jiang Fix For: 0.5 Eagle 0.5 updates the rest api interface and UI need also update for support the api. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-557) Setup Eagle v0.5 Documentation Site Layout
[ https://issues.apache.org/jira/browse/EAGLE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528229#comment-15528229 ] Michael Wu commented on EAGLE-557: -- Setup a mkdocs service on demo node, listening on port 8000. > 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 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #459: [Minor] Update History Job Counting API
GitHub user qingwen220 opened a pull request: https://github.com/apache/incubator-eagle/pull/459 [Minor] Update History Job Counting API add a query parameter 'jobType' You can merge this pull request into a Git repository by running: $ git pull https://github.com/qingwen220/incubator-eagle historyJob Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/459.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 #459 commit 5dc4e9094357081fd06b4d933d5cb0febae71710 Author: Qingwen Zhao Date: 2016-09-23T07:14:00Z add jobType filter in JobHistory count commit 619f9c231645b506f3e335f2421d9005748d247a Author: Qingwen Zhao Date: 2016-09-27T03:37:39Z Merge branch 'master' of https://github.com/apache/incubator-eagle into historyJob commit fb3bde18c53bfa4ed52d359082b9404d3a44ffb0 Author: Qingwen Zhao Date: 2016-09-27T03:41:16Z Merge branch 'master' of https://github.com/apache/incubator-eagle into historyJob --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Resolved] (EAGLE-573) NPE when apply change of 569
[ https://issues.apache.org/jira/browse/EAGLE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Su Ralph resolved EAGLE-573. Resolution: Fixed > NPE when apply change of 569 > > > Key: EAGLE-573 > URL: https://issues.apache.org/jira/browse/EAGLE-573 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: v0.5.0 > > > There is an NPE when policyId not in publishment plugin mapping. This often > happen metadata refresh happens. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #458: [EAGLE-573]: NPE when apply change of EAG...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/458 --- 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-573) NPE when apply change of 569
[ https://issues.apache.org/jira/browse/EAGLE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527896#comment-15527896 ] ASF GitHub Bot commented on EAGLE-573: -- GitHub user RalphSu opened a pull request: https://github.com/apache/incubator-eagle/pull/458 [EAGLE-573]: NPE when apply change of EAGLE-569 Fix by do npe check in concurret case. Author : ralphsu You can merge this pull request into a Git repository by running: $ git pull https://github.com/RalphSu/incubator-eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/458.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 #458 commit ed757ba563699b24574f3a3dd6c127d5db7634db Author: Ralph, Su Date: 2016-09-28T00:22:43Z [EAGLE-573]: NPE when apply change of EAGLE-569 Author : ralphsu > NPE when apply change of 569 > > > Key: EAGLE-573 > URL: https://issues.apache.org/jira/browse/EAGLE-573 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: v0.5.0 > > > There is an NPE when policyId not in publishment plugin mapping. This often > happen metadata refresh happens. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-573) NPE when apply change of 569
[ https://issues.apache.org/jira/browse/EAGLE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527898#comment-15527898 ] ASF GitHub Bot commented on EAGLE-573: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/458 > NPE when apply change of 569 > > > Key: EAGLE-573 > URL: https://issues.apache.org/jira/browse/EAGLE-573 > Project: Eagle > Issue Type: Sub-task >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: v0.5.0 > > > There is an NPE when policyId not in publishment plugin mapping. This often > happen metadata refresh happens. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #458: [EAGLE-573]: NPE when apply change of EAG...
GitHub user RalphSu opened a pull request: https://github.com/apache/incubator-eagle/pull/458 [EAGLE-573]: NPE when apply change of EAGLE-569 Fix by do npe check in concurret case. Author : ralphsu You can merge this pull request into a Git repository by running: $ git pull https://github.com/RalphSu/incubator-eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/458.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 #458 commit ed757ba563699b24574f3a3dd6c127d5db7634db Author: Ralph, Su Date: 2016-09-28T00:22:43Z [EAGLE-573]: NPE when apply change of EAGLE-569 Author : ralphsu --- 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-573) NPE when apply change of 569
Su Ralph created EAGLE-573: -- Summary: NPE when apply change of 569 Key: EAGLE-573 URL: https://issues.apache.org/jira/browse/EAGLE-573 Project: Eagle Issue Type: Sub-task Affects Versions: v0.5.0 Reporter: Su Ralph Assignee: Su Ralph Fix For: v0.5.0 There is an NPE when policyId not in publishment plugin mapping. This often happen metadata refresh happens. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-572) AlertEngine: Metadata API doesn't do validation of metadata
Su Ralph created EAGLE-572: -- Summary: AlertEngine: Metadata API doesn't do validation of metadata Key: EAGLE-572 URL: https://issues.apache.org/jira/browse/EAGLE-572 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Su Ralph Assignee: Su Ralph Fix For: v0.5.0 Current metadata api only do minor validation of the given metadata. User is able to submit stream definition with duplicated field name. Ideally, Metadata API should be first place to avoid user post invalid metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-571) AlertEngine: Topology should support loopback topic created after policy deployed
Su Ralph created EAGLE-571: -- Summary: AlertEngine: Topology should support loopback topic created after policy deployed Key: EAGLE-571 URL: https://issues.apache.org/jira/browse/EAGLE-571 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Su Ralph Assignee: Su Ralph Fix For: v0.5.0 when processing havetopic1 -> policy1 -> topic2; and topic2 -> policy2 -> topic2 case, the topology is not able to start. Since the topic2 initialization failure (topic2 not create yet) would make topic1 not able to be consumed. Thus chicken-egg problem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-569) AlertPublishImpl: Concurrency : Inplace change metadata cause concurrent modification issue
[ https://issues.apache.org/jira/browse/EAGLE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526842#comment-15526842 ] ASF GitHub Bot commented on EAGLE-569: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/457 > AlertPublishImpl: Concurrency : Inplace change metadata cause concurrent > modification issue > --- > > Key: EAGLE-569 > URL: https://issues.apache.org/jira/browse/EAGLE-569 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph >Priority: Critical > Fix For: v0.5.0 > > > We are try to re-use eagle alert module as part our streaming processing > core, during test, we found below error. > 6700java.util.ConcurrentModificationException at > java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) at > java.util.ArrayList$Itr.next(ArrayList.java:851) at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:74) > It happens to be in AlertPublisherImpl, the metadata change is doing inplace > update, which cause the concurrency issue when the bolt is continuing ingest > data. > This exception should cause following data stream not able to be published. > Hence be blocker -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EAGLE-569) AlertPublishImpl: Concurrency : Inplace change metadata cause concurrent modification issue
[ https://issues.apache.org/jira/browse/EAGLE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Su Ralph resolved EAGLE-569. Resolution: Fixed > AlertPublishImpl: Concurrency : Inplace change metadata cause concurrent > modification issue > --- > > Key: EAGLE-569 > URL: https://issues.apache.org/jira/browse/EAGLE-569 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph >Priority: Critical > Fix For: v0.5.0 > > > We are try to re-use eagle alert module as part our streaming processing > core, during test, we found below error. > 6700java.util.ConcurrentModificationException at > java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) at > java.util.ArrayList$Itr.next(ArrayList.java:851) at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:74) > It happens to be in AlertPublisherImpl, the metadata change is doing inplace > update, which cause the concurrency issue when the bolt is continuing ingest > data. > This exception should cause following data stream not able to be published. > Hence be blocker -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #457: [EAGLE-569]: AlertPublishImpl: Concurrenc...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/457 --- 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-569) AlertPublishImpl: Concurrency : Inplace change metadata cause concurrent modification issue
[ https://issues.apache.org/jira/browse/EAGLE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526832#comment-15526832 ] ASF GitHub Bot commented on EAGLE-569: -- Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/457 Fix to use copy&swap way to refresh metadata changes. > AlertPublishImpl: Concurrency : Inplace change metadata cause concurrent > modification issue > --- > > Key: EAGLE-569 > URL: https://issues.apache.org/jira/browse/EAGLE-569 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph >Priority: Critical > Fix For: v0.5.0 > > > We are try to re-use eagle alert module as part our streaming processing > core, during test, we found below error. > 6700java.util.ConcurrentModificationException at > java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) at > java.util.ArrayList$Itr.next(ArrayList.java:851) at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:74) > It happens to be in AlertPublisherImpl, the metadata change is doing inplace > update, which cause the concurrency issue when the bolt is continuing ingest > data. > This exception should cause following data stream not able to be published. > Hence be blocker -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-569) AlertPublishImpl: Concurrency : Inplace change metadata cause concurrent modification issue
[ https://issues.apache.org/jira/browse/EAGLE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526823#comment-15526823 ] ASF GitHub Bot commented on EAGLE-569: -- GitHub user RalphSu opened a pull request: https://github.com/apache/incubator-eagle/pull/457 [EAGLE-569]: AlertPublishImpl: Concurrency : Inplace change metadata … Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). ---> …cause concurrent modification issue Author : ralphsu You can merge this pull request into a Git repository by running: $ git pull https://github.com/RalphSu/incubator-eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/457.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 #457 > AlertPublishImpl: Concurrency : Inplace change metadata cause concurrent > modification issue > --- > > Key: EAGLE-569 > URL: https://issues.apache.org/jira/browse/EAGLE-569 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph >Priority: Critical > Fix For: v0.5.0 > > > We are try to re-use eagle alert module as part our streaming processing > core, during test, we found below error. > 6700java.util.ConcurrentModificationException at > java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) at > java.util.ArrayList$Itr.next(ArrayList.java:851) at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:74) > It happens to be in AlertPublisherImpl, the metadata change is doing inplace > update, which cause the concurrency issue when the bolt is continuing ingest > data. > This exception should cause following data stream not able to be published. > Hence be blocker -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #457: [EAGLE-569]: AlertPublishImpl: Concurrency : Inp...
Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/457 Fix to use copy&swap way to refresh metadata changes. --- 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 #457: [EAGLE-569]: AlertPublishImpl: Concurrenc...
GitHub user RalphSu opened a pull request: https://github.com/apache/incubator-eagle/pull/457 [EAGLE-569]: AlertPublishImpl: Concurrency : Inplace change metadata ⦠Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). ---> â¦cause concurrent modification issue Author : ralphsu You can merge this pull request into a Git repository by running: $ git pull https://github.com/RalphSu/incubator-eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/457.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 #457 --- 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] [Assigned] (EAGLE-569) AlertPublishImpl: Concurrency : Inplace change metadata cause concurrent modification issue
[ https://issues.apache.org/jira/browse/EAGLE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Su Ralph reassigned EAGLE-569: -- Assignee: Su Ralph (was: Garrett Li) > AlertPublishImpl: Concurrency : Inplace change metadata cause concurrent > modification issue > --- > > Key: EAGLE-569 > URL: https://issues.apache.org/jira/browse/EAGLE-569 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph >Priority: Critical > Fix For: v0.5.0 > > > We are try to re-use eagle alert module as part our streaming processing > core, during test, we found below error. > 6700java.util.ConcurrentModificationException at > java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) at > java.util.ArrayList$Itr.next(ArrayList.java:851) at > org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:74) > It happens to be in AlertPublisherImpl, the metadata change is doing inplace > update, which cause the concurrency issue when the bolt is continuing ingest > data. > This exception should cause following data stream not able to be published. > Hence be blocker -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-567) Enhance Slack publish format
[ https://issues.apache.org/jira/browse/EAGLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526556#comment-15526556 ] ASF GitHub Bot commented on EAGLE-567: -- Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/456 https://issues.apache.org/jira/browse/EAGLE-570 for continue refactor. > Enhance Slack publish format > > > Key: EAGLE-567 > URL: https://issues.apache.org/jira/browse/EAGLE-567 > Project: Eagle > Issue Type: Improvement >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > Currently message publish to Slack is raw String, and this is not very clear > for user. > So need to add format for it for better viewing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #456: EAGLE-567: Enhance Slack publish format
Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/456 https://issues.apache.org/jira/browse/EAGLE-570 for continue refactor. --- 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-567) Enhance Slack publish format
[ https://issues.apache.org/jira/browse/EAGLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526554#comment-15526554 ] ASF GitHub Bot commented on EAGLE-567: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/456 > Enhance Slack publish format > > > Key: EAGLE-567 > URL: https://issues.apache.org/jira/browse/EAGLE-567 > Project: Eagle > Issue Type: Improvement >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > Currently message publish to Slack is raw String, and this is not very clear > for user. > So need to add format for it for better viewing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #456: EAGLE-567: Enhance Slack publish format
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/456 --- 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-570) Refactor: Make sure engine publisher only have general feature.
Su Ralph created EAGLE-570: -- Summary: Refactor: Make sure engine publisher only have general feature. Key: EAGLE-570 URL: https://issues.apache.org/jira/browse/EAGLE-570 Project: Eagle Issue Type: Sub-task Affects Versions: v0.5.0 Reporter: Su Ralph Assignee: Zeng, Bryant Fix For: v0.5.0 Eagle-567 intend to provide better formatting of slack channel message. But the implementation introduce too much specific logic that beyond a common alerting engine should have. Need to refactor to move the specific logic to either vendor specific extension or have configurable formatting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-566) add dedup fields into publishment compare consideration
[ https://issues.apache.org/jira/browse/EAGLE-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526517#comment-15526517 ] ASF GitHub Bot commented on EAGLE-566: -- Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/454 https://issues.apache.org/jira/browse/EAGLE-566. This PR fixes the incorrect implement of equal() and hashcode(), which cause the alertPublisherBolt not able to detect config change. Merged > add dedup fields into publishment compare consideration > --- > > Key: EAGLE-566 > URL: https://issues.apache.org/jira/browse/EAGLE-566 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > add dedup fields into publishment compare consideration, without it, > publishment dedup fields change won't be reloaded -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #454: [EAGLE-566] add dedup fields into publishment co...
Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/454 https://issues.apache.org/jira/browse/EAGLE-566. This PR fixes the incorrect implement of equal() and hashcode(), which cause the alertPublisherBolt not able to detect config change. Merged --- 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-566) add dedup fields into publishment compare consideration
[ https://issues.apache.org/jira/browse/EAGLE-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526514#comment-15526514 ] ASF GitHub Bot commented on EAGLE-566: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/454 > add dedup fields into publishment compare consideration > --- > > Key: EAGLE-566 > URL: https://issues.apache.org/jira/browse/EAGLE-566 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > add dedup fields into publishment compare consideration, without it, > publishment dedup fields change won't be reloaded -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #454: [EAGLE-566] add dedup fields into publish...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-eagle/pull/454 --- 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 #456: EAGLE-567: Enhance Slack publish format
Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/456 We could need to refactor here, not to have these check in here. --- 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-567) Enhance Slack publish format
[ https://issues.apache.org/jira/browse/EAGLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526504#comment-15526504 ] ASF GitHub Bot commented on EAGLE-567: -- Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/456 We could need to refactor here, not to have these check in here. > Enhance Slack publish format > > > Key: EAGLE-567 > URL: https://issues.apache.org/jira/browse/EAGLE-567 > Project: Eagle > Issue Type: Improvement >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > Currently message publish to Slack is raw String, and this is not very clear > for user. > So need to add format for it for better viewing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EAGLE-567) Enhance Slack publish format
[ https://issues.apache.org/jira/browse/EAGLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526488#comment-15526488 ] Su Ralph commented on EAGLE-567: This make the slack message much more pretty. Thanks. > Enhance Slack publish format > > > Key: EAGLE-567 > URL: https://issues.apache.org/jira/browse/EAGLE-567 > Project: Eagle > Issue Type: Improvement >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > Currently message publish to Slack is raw String, and this is not very clear > for user. > So need to add format for it for better viewing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-569) AlertPublishImpl: Concurrency : Inplace change metadata cause concurrent modification issue
Su Ralph created EAGLE-569: -- Summary: AlertPublishImpl: Concurrency : Inplace change metadata cause concurrent modification issue Key: EAGLE-569 URL: https://issues.apache.org/jira/browse/EAGLE-569 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Su Ralph Assignee: Garrett Li Priority: Critical Fix For: v0.5.0 We are try to re-use eagle alert module as part our streaming processing core, during test, we found below error. 6700java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) at java.util.ArrayList$Itr.next(ArrayList.java:851) at org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:74) It happens to be in AlertPublisherImpl, the metadata change is doing inplace update, which cause the concurrency issue when the bolt is continuing ingest data. This exception should cause following data stream not able to be published. Hence be blocker -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-568) Set max retry times for HDFS problems, otherwise skip instead of blocking whole topology
[
https://issues.apache.org/jira/browse/EAGLE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-568:
---
Description:
h1. Problem and Exception
{code}
2016-09-23 16:20:03 Thread-2-mrHistoryJobExecutor
org.apache.eagle.jpm.mr.history.storm.JobHistorySpout [ERROR] fail crawling job
history file and continue ...
java.lang.RuntimeException: org.apache.hadoop.hdfs.BlockMissingException: Could
not obtain block:
BP-1687617170-10.8.211.11-1404135347814:blk_6965456919_1107923643088
file=/mapred/history/done/2016/09/23/000716/job_1470077190071_716284_conf.xml
at
org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2398)
~[stormjar.jar:na]
at
org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2261)
~[stormjar.jar:na]
at
org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2168)
~[stormjar.jar:na]
at
org.apache.hadoop.conf.Configuration.iterator(Configuration.java:2210)
~[stormjar.jar:na]
at java.lang.Iterable.forEach(Iterable.java:74) ~[na:1.8.0_91]
at org.apache.eagle.jpm.util.Utils.fetchJobType(Utils.java:112)
~[stormjar.jar:na]
at
org.apache.eagle.jpm.mr.history.parser.JHFEventReaderBase.(JHFEventReaderBase.java:121)
~[stormjar.jar:na]
at
org.apache.eagle.jpm.mr.history.parser.JHFMRVer2EventReader.(JHFMRVer2EventReader.java:47)
~[stormjar.jar:na]
at
org.apache.eagle.jpm.mr.history.parser.JHFParserFactory.getParser(JHFParserFactory.java:49)
~[stormjar.jar:na]
at
org.apache.eagle.jpm.mr.history.crawler.DefaultJHFInputStreamCallback.onInputStream(DefaultJHFInputStreamCallback.java:55)
~[stormjar.jar:na]
at
org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO.readFileContent(AbstractJobHistoryDAO.java:163)
~[stormjar.jar:na]
at
org.apache.eagle.jpm.mr.history.crawler.JHFCrawlerDriverImpl.crawl(JHFCrawlerDriverImpl.java:173)
~[stormjar.jar:na]
at
org.apache.eagle.jpm.mr.history.storm.JobHistorySpout.nextTuple(JobHistorySpout.java:166)
~[stormjar.jar:na]
at
backtype.storm.daemon.executor$fn__5629$fn__5644$fn__5673.invoke(executor.clj:585)
[storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
at backtype.storm.util$async_loop$fn__452.invoke(util.clj:465)
[storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
at clojure.lang.AFn.run(AFn.java:24) [clojure-1.5.1.jar:na]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
Caused by: org.apache.hadoop.hdfs.BlockMissingException: Could not obtain
block: BP-1687617170-10.8.211.11-1404135347814:blk_6965456919_1107923643088
file=/mapred/history/done/2016/09/23/000716/job_1470077190071_716284_conf.xml
at
org.apache.hadoop.hdfs.DFSInputStream.chooseDataNode(DFSInputStream.java:880)
~[stormjar.jar:na]
at
org.apache.hadoop.hdfs.DFSInputStream.blockSeekTo(DFSInputStream.java:560)
~[stormjar.jar:na]
at
org.apache.hadoop.hdfs.DFSInputStream.readWithStrategy(DFSInputStream.java:790)
~[stormjar.jar:na]
at org.apache.hadoop.hdfs.DFSInputStream.read(DFSInputStream.java:837)
~[stormjar.jar:na]
at org.apache.hadoop.hdfs.DFSInputStream.read(DFSInputStream.java:645)
~[stormjar.jar:na]
at java.io.FilterInputStream.read(FilterInputStream.java:83)
~[na:1.8.0_91]
at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager$RewindableInputStream.read(XMLEntityManager.java:2899)
~[na:1.8.0_91]
at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:674)
~[na:1.8.0_91]
at
com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:189)
~[na:1.8.0_91]
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:812)
~[na:1.8.0_91]
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
~[na:1.8.0_91]
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
~[na:1.8.0_91]
at
com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:243)
~[na:1.8.0_91]
at
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:339)
~[na:1.8.0_91]
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121)
~[na:1.8.0_91]
at org.apache.hadoop.conf.Configuration.parse(Configuration.java:2239)
~[stormjar.jar:na]
at
org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2312)
~[stormjar.jar:na]
... 16 common frames omitted
{code}
h1. Proposal Solution
Set max retry times for HDFS problems, otherwise skip instead of blocking whole
topology
was:
{code}
2016-09-23 16:20:03 Thread-2-mrHistoryJobExecutor
org.apache.eagle.jpm.mr.history.storm.JobHistorySpout [ERROR] fail crawling job
histo
[jira] [Updated] (EAGLE-568) Set max retry times for HDFS problems, otherwise skip instead of blocking whole topology
[
https://issues.apache.org/jira/browse/EAGLE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-568:
---
Labels: eagle-jpm eagle-jpm-mr-history (was: )
> Set max retry times for HDFS problems, otherwise skip instead of blocking
> whole topology
>
>
> Key: EAGLE-568
> URL: https://issues.apache.org/jira/browse/EAGLE-568
> Project: Eagle
> Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: wujinhu
> Labels: eagle-jpm, eagle-jpm-mr-history
> Fix For: v0.5.0
>
>
> h1. Problem and Exception
> {code}
> 2016-09-23 16:20:03 Thread-2-mrHistoryJobExecutor
> org.apache.eagle.jpm.mr.history.storm.JobHistorySpout [ERROR] fail crawling
> job history file and continue ...
> java.lang.RuntimeException: org.apache.hadoop.hdfs.BlockMissingException:
> Could not obtain block:
> BP-1687617170-10.8.211.11-1404135347814:blk_6965456919_1107923643088
> file=/mapred/history/done/2016/09/23/000716/job_1470077190071_716284_conf.xml
> at
> org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2398)
> ~[stormjar.jar:na]
> at
> org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2261)
> ~[stormjar.jar:na]
> at
> org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2168)
> ~[stormjar.jar:na]
> at
> org.apache.hadoop.conf.Configuration.iterator(Configuration.java:2210)
> ~[stormjar.jar:na]
> at java.lang.Iterable.forEach(Iterable.java:74) ~[na:1.8.0_91]
> at org.apache.eagle.jpm.util.Utils.fetchJobType(Utils.java:112)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.parser.JHFEventReaderBase.(JHFEventReaderBase.java:121)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.parser.JHFMRVer2EventReader.(JHFMRVer2EventReader.java:47)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.parser.JHFParserFactory.getParser(JHFParserFactory.java:49)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.crawler.DefaultJHFInputStreamCallback.onInputStream(DefaultJHFInputStreamCallback.java:55)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO.readFileContent(AbstractJobHistoryDAO.java:163)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.crawler.JHFCrawlerDriverImpl.crawl(JHFCrawlerDriverImpl.java:173)
> ~[stormjar.jar:na]
> at
> org.apache.eagle.jpm.mr.history.storm.JobHistorySpout.nextTuple(JobHistorySpout.java:166)
> ~[stormjar.jar:na]
> at
> backtype.storm.daemon.executor$fn__5629$fn__5644$fn__5673.invoke(executor.clj:585)
> [storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
> at backtype.storm.util$async_loop$fn__452.invoke(util.clj:465)
> [storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
> at clojure.lang.AFn.run(AFn.java:24) [clojure-1.5.1.jar:na]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
> Caused by: org.apache.hadoop.hdfs.BlockMissingException: Could not obtain
> block: BP-1687617170-10.8.211.11-1404135347814:blk_6965456919_1107923643088
> file=/mapred/history/done/2016/09/23/000716/job_1470077190071_716284_conf.xml
> at
> org.apache.hadoop.hdfs.DFSInputStream.chooseDataNode(DFSInputStream.java:880)
> ~[stormjar.jar:na]
> at
> org.apache.hadoop.hdfs.DFSInputStream.blockSeekTo(DFSInputStream.java:560)
> ~[stormjar.jar:na]
> at
> org.apache.hadoop.hdfs.DFSInputStream.readWithStrategy(DFSInputStream.java:790)
> ~[stormjar.jar:na]
> at
> org.apache.hadoop.hdfs.DFSInputStream.read(DFSInputStream.java:837)
> ~[stormjar.jar:na]
> at
> org.apache.hadoop.hdfs.DFSInputStream.read(DFSInputStream.java:645)
> ~[stormjar.jar:na]
> at java.io.FilterInputStream.read(FilterInputStream.java:83)
> ~[na:1.8.0_91]
> at
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager$RewindableInputStream.read(XMLEntityManager.java:2899)
> ~[na:1.8.0_91]
> at
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:674)
> ~[na:1.8.0_91]
> at
> com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:189)
> ~[na:1.8.0_91]
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:812)
> ~[na:1.8.0_91]
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
> ~[na:1.8.0_91]
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
> ~[na:1.8.0_91]
> at
> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:243)
[jira] [Created] (EAGLE-568) Set max retry times for HDFS problems, otherwise skip instead of blocking whole topology
Hao Chen created EAGLE-568:
--
Summary: Set max retry times for HDFS problems, otherwise skip
instead of blocking whole topology
Key: EAGLE-568
URL: https://issues.apache.org/jira/browse/EAGLE-568
Project: Eagle
Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: wujinhu
Fix For: v0.5.0
{code}
2016-09-23 16:20:03 Thread-2-mrHistoryJobExecutor
org.apache.eagle.jpm.mr.history.storm.JobHistorySpout [ERROR] fail crawling job
history file and continue ...
java.lang.RuntimeException: org.apache.hadoop.hdfs.BlockMissingException: Could
not obtain block:
BP-1687617170-10.8.211.11-1404135347814:blk_6965456919_1107923643088
file=/mapred/history/done/2016/09/23/000716/job_1470077190071_716284_conf.xml
at
org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2398)
~[stormjar.jar:na]
at
org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2261)
~[stormjar.jar:na]
at
org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2168)
~[stormjar.jar:na]
at
org.apache.hadoop.conf.Configuration.iterator(Configuration.java:2210)
~[stormjar.jar:na]
at java.lang.Iterable.forEach(Iterable.java:74) ~[na:1.8.0_91]
at org.apache.eagle.jpm.util.Utils.fetchJobType(Utils.java:112)
~[stormjar.jar:na]
at
org.apache.eagle.jpm.mr.history.parser.JHFEventReaderBase.(JHFEventReaderBase.java:121)
~[stormjar.jar:na]
at
org.apache.eagle.jpm.mr.history.parser.JHFMRVer2EventReader.(JHFMRVer2EventReader.java:47)
~[stormjar.jar:na]
at
org.apache.eagle.jpm.mr.history.parser.JHFParserFactory.getParser(JHFParserFactory.java:49)
~[stormjar.jar:na]
at
org.apache.eagle.jpm.mr.history.crawler.DefaultJHFInputStreamCallback.onInputStream(DefaultJHFInputStreamCallback.java:55)
~[stormjar.jar:na]
at
org.apache.eagle.jpm.mr.history.crawler.AbstractJobHistoryDAO.readFileContent(AbstractJobHistoryDAO.java:163)
~[stormjar.jar:na]
at
org.apache.eagle.jpm.mr.history.crawler.JHFCrawlerDriverImpl.crawl(JHFCrawlerDriverImpl.java:173)
~[stormjar.jar:na]
at
org.apache.eagle.jpm.mr.history.storm.JobHistorySpout.nextTuple(JobHistorySpout.java:166)
~[stormjar.jar:na]
at
backtype.storm.daemon.executor$fn__5629$fn__5644$fn__5673.invoke(executor.clj:585)
[storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
at backtype.storm.util$async_loop$fn__452.invoke(util.clj:465)
[storm-core-0.9.3.2.2.0.0-2041.jar:0.9.3.2.2.0.0-2041]
at clojure.lang.AFn.run(AFn.java:24) [clojure-1.5.1.jar:na]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
Caused by: org.apache.hadoop.hdfs.BlockMissingException: Could not obtain
block: BP-1687617170-10.8.211.11-1404135347814:blk_6965456919_1107923643088
file=/mapred/history/done/2016/09/23/000716/job_1470077190071_716284_conf.xml
at
org.apache.hadoop.hdfs.DFSInputStream.chooseDataNode(DFSInputStream.java:880)
~[stormjar.jar:na]
at
org.apache.hadoop.hdfs.DFSInputStream.blockSeekTo(DFSInputStream.java:560)
~[stormjar.jar:na]
at
org.apache.hadoop.hdfs.DFSInputStream.readWithStrategy(DFSInputStream.java:790)
~[stormjar.jar:na]
at org.apache.hadoop.hdfs.DFSInputStream.read(DFSInputStream.java:837)
~[stormjar.jar:na]
at org.apache.hadoop.hdfs.DFSInputStream.read(DFSInputStream.java:645)
~[stormjar.jar:na]
at java.io.FilterInputStream.read(FilterInputStream.java:83)
~[na:1.8.0_91]
at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager$RewindableInputStream.read(XMLEntityManager.java:2899)
~[na:1.8.0_91]
at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:674)
~[na:1.8.0_91]
at
com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:189)
~[na:1.8.0_91]
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:812)
~[na:1.8.0_91]
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
~[na:1.8.0_91]
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
~[na:1.8.0_91]
at
com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:243)
~[na:1.8.0_91]
at
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:339)
~[na:1.8.0_91]
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121)
~[na:1.8.0_91]
at org.apache.hadoop.conf.Configuration.parse(Configuration.java:2239)
~[stormjar.jar:na]
at
org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2312)
~[stormjar.jar:na]
... 16 common frames omitted
{code}
--
This message was sent by Atlassian JIR
[GitHub] incubator-eagle pull request #456: EAGLE-567: Enhance Slack publish format
GitHub user mizeng opened a pull request: https://github.com/apache/incubator-eagle/pull/456 EAGLE-567: Enhance Slack publish format Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/mizeng/incubator-eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/456.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 #456 commit 4a5078bdf9e75bc8e7e69029026b15af3a0de0af Author: mizeng Date: 2016-09-27T07:15:16Z EAGLE-567: Enhance Slack publish format --- 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-567) Enhance Slack publish format
[ https://issues.apache.org/jira/browse/EAGLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15525332#comment-15525332 ] ASF GitHub Bot commented on EAGLE-567: -- GitHub user mizeng opened a pull request: https://github.com/apache/incubator-eagle/pull/456 EAGLE-567: Enhance Slack publish format Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/mizeng/incubator-eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/456.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 #456 commit 4a5078bdf9e75bc8e7e69029026b15af3a0de0af Author: mizeng Date: 2016-09-27T07:15:16Z EAGLE-567: Enhance Slack publish format > Enhance Slack publish format > > > Key: EAGLE-567 > URL: https://issues.apache.org/jira/browse/EAGLE-567 > Project: Eagle > Issue Type: Improvement >Reporter: Zeng, Bryant >Assignee: Zeng, Bryant > > Currently message publish to Slack is raw String, and this is not very clear > for user. > So need to add format for it for better viewing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-567) Enhance Slack publish format
Zeng, Bryant created EAGLE-567: -- Summary: Enhance Slack publish format Key: EAGLE-567 URL: https://issues.apache.org/jira/browse/EAGLE-567 Project: Eagle Issue Type: Improvement Reporter: Zeng, Bryant Assignee: Zeng, Bryant Currently message publish to Slack is raw String, and this is not very clear for user. So need to add format for it for better viewing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-566) add dedup fields into publishment compare consideration
Garrett Li created EAGLE-566: Summary: add dedup fields into publishment compare consideration Key: EAGLE-566 URL: https://issues.apache.org/jira/browse/EAGLE-566 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Garrett Li Assignee: Garrett Li Fix For: v0.5.0 add dedup fields into publishment compare consideration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EAGLE-566) add dedup fields into publishment compare consideration
[ https://issues.apache.org/jira/browse/EAGLE-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garrett Li updated EAGLE-566: - Description: add dedup fields into publishment compare consideration, without it, publishment dedup fields change won't be reloaded (was: add dedup fields into publishment compare consideration) > add dedup fields into publishment compare consideration > --- > > Key: EAGLE-566 > URL: https://issues.apache.org/jira/browse/EAGLE-566 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Fix For: v0.5.0 > > > add dedup fields into publishment compare consideration, without it, > publishment dedup fields change won't be reloaded -- This message was sent by Atlassian JIRA (v6.3.4#6332)
