date:20160928

[jira] [Commented] (EAGLE-432) Application status monitoring

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-432:
--

Github user asfgit closed the pull request at:

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


> 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

2016-09-28 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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 #465: EAGLE-578: Make dedup state value case in...

2016-09-28 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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-578) Make dedup state value case insensitive

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-578:
--

Github user asfgit closed the pull request at:

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


> Make dedup state value case insensitive
> ---
>
> Key: EAGLE-578
> URL: https://issues.apache.org/jira/browse/EAGLE-578
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> Currently our dedup feature supports both stateful and stateless dedup. For 
> stateful dedup, we are relying the state transition to do the dedup. However, 
> the state might be closed or CLOSED, we'd better to make it case insensitive.



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

[jira] [Commented] (EAGLE-578) Make dedup state value case insensitive

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-578:
--

GitHub user garrettlish opened a pull request:

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

EAGLE-578: Make dedup state value case insensitive

Currently our dedup feature supports both stateful and stateless dedup. For 
stateful dedup, we are relying the state transition to do the dedup. However, 
the state might be in different case (such as closed, CLOSED), we'd better to 
make it case insensitive.

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/465.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 #465


commit 22d27f6a5003b90fe6572b5241ac1adc61c4dc66
Author: Xiancheng Li 
Date:   2016-09-29T02:52:07Z

EAGLE-578: Make dedup state value case insensitive




> Make dedup state value case insensitive
> ---
>
> Key: EAGLE-578
> URL: https://issues.apache.org/jira/browse/EAGLE-578
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> Currently our dedup feature supports both stateful and stateless dedup. For 
> stateful dedup, we are relying the state transition to do the dedup. However, 
> the state might be closed or CLOSED, we'd better to make it case insensitive.



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

[GitHub] incubator-eagle pull request #465: EAGLE-578: Make dedup state value case in...

2016-09-28 Thread garrettlish

GitHub user garrettlish opened a pull request:

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

EAGLE-578: Make dedup state value case insensitive

Currently our dedup feature supports both stateful and stateless dedup. For 
stateful dedup, we are relying the state transition to do the dedup. However, 
the state might be in different case (such as closed, CLOSED), we'd better to 
make it case insensitive.

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/465.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 #465


commit 22d27f6a5003b90fe6572b5241ac1adc61c4dc66
Author: Xiancheng Li 
Date:   2016-09-29T02:52:07Z

EAGLE-578: Make dedup state value case insensitive




---
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-578) Make dedup state value case insensitive

2016-09-28 Thread Garrett Li (JIRA)

Garrett Li created EAGLE-578:


 Summary: Make dedup state value case insensitive
 Key: EAGLE-578
 URL: https://issues.apache.org/jira/browse/EAGLE-578
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Garrett Li
Assignee: Garrett Li
 Fix For: v0.5.0


Currently our dedup feature supports both stateful and stateless dedup. For 
stateful dedup, we are relying the state transition to do the dedup. However, 
the state might be closed or CLOSED, we'd better to make it case insensitive.



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

[jira] [Resolved] (EAGLE-576) Dedup enhancements

2016-09-28 Thread Garrett Li (JIRA)


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

Garrett Li resolved EAGLE-576.
--
Resolution: Fixed

merged

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

[GitHub] incubator-eagle issue #452: update joiner from storm to google library

2016-09-28 Thread garrettlish

Github user garrettlish commented on the issue:

https://github.com/apache/incubator-eagle/pull/452
  
@yonzhang add description, thanks for reminder


---
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 #452: update joiner from storm to google library

2016-09-28 Thread yonzhang

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/452
  
@garrettlish please add description to this PR?


---
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-550) Add Alert publish implementation for Slack

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-550:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/442
  
@garrettlish can you please add more information to this PR so people can 
learn what are the changes for?


> Add Alert publish implementation for Slack
> --
>
> Key: EAGLE-550
> URL: https://issues.apache.org/jira/browse/EAGLE-550
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Zeng, Bryant
>Assignee: Zeng, Bryant
>
> Add one more publish implement (Slack) for Alert.
> How to implement
> 1. Here uses a lib "simple-slack-api" to connecting to Slack and publish 
> alert messages to Slack.
> 2. Add one more publisher of Slack which extends "AbstractPublishPlugin" to 
> process received AlertStreamEvent, and according to Slack config which 
> defined in publishment.json to send messages.
> How to use
> 1. Create a bot user in Slack, and remember its token.
> 2. Create some channels if you want send messages to if they do not exist.
> 3. Add your bot user to these channels.
> 4. Then define Slack config and declare to use Slack publisher in config file 
> such as below (Especially the "type" and "properties". Here urltemplate will 
> form an output url link based on docId if downstream have it.), we can use it 
> very easily:
>  {
> "name": "test-slack-output",
> "type": 
> "org.apache.eagle.alert.engine.publisher.impl.AlertSlackPublisher",
> "policyIds": [
>   "switch_check"
> ],
> "properties": {
>   "token": "your token",
>   "channels": "your channel1, your channel2",
>   "severitys": "CRITICAL",
>   "urltemplate": "your template/?id=%s"
> },
> "dedupIntervalMin": "PT1M",
> "dedupFields": [
>   "appname"
> ],
> "serializer": 
> "org.apache.eagle.alert.engine.publisher.impl.StringEventSerializer"
>   }
> Something about the metadata schema
> 1. token: your bot user token. 
> 2. channels: Slack channel names.
> 3. severitys: which severity level alert message you want to send to Slack. 
> Other level message will be skipped.
> 4. urltemplate: used to form an output url link based on docId if downstream 
> have it. A typical use case will be that downstream stored all the alerts in 
> Elasticsearch, so we can previously append an ES link in the slack message.



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

[GitHub] incubator-eagle issue #442: EAGLE-550: periodically clean up dedup cache

2016-09-28 Thread yonzhang

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/442
  
@garrettlish can you please add more information to this PR so people can 
learn what are the changes for?


---
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-547) Fix duplicated view path

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-547:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/438
  
@haoch better please to explain why view path is duplicated.


> Fix duplicated view path
> 
>
> Key: EAGLE-547
> URL: https://issues.apache.org/jira/browse/EAGLE-547
> Project: Eagle
>  Issue Type: Bug
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>




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

[GitHub] incubator-eagle issue #438: EAGLE-547 Resolve duplicated view path

2016-09-28 Thread yonzhang

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/438
  
@haoch better please to explain why view path is duplicated.


---
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-544) Enhance dedup to support extended deduplicator

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-544:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/437
  
@garrettlish can you please add good information to this PR?


> Enhance dedup to support extended deduplicator
> --
>
> Key: EAGLE-544
> URL: https://issues.apache.org/jira/browse/EAGLE-544
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>




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

[GitHub] incubator-eagle issue #437: EAGLE-544: Enhance dedup to support extended ded...

2016-09-28 Thread yonzhang

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/437
  
@garrettlish can you please add good information to this PR?


---
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 #433: Fix conflict

2016-09-28 Thread yonzhang

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/433
  
@wujinhu can you elaborate what are the changes for in this PR? "Fix 
conflict" is a very generic title for one PR :-)


---
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-538) Add Mapreduce task level apis

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-538:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/432
  
@qingwen220 can you please add good description for this big PR?


> Add Mapreduce task level apis 
> --
>
> Key: EAGLE-538
> URL: https://issues.apache.org/jira/browse/EAGLE-538
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> *Running task count by duration*
> http://localhost:9090/rest/mrTasks/taskCountsByDuration?jobId=job_1=apollo=0,30,60=3
> *Task distribution by counterName*
> http://localhost:9090/rest/mrTasks/taskDistribution/HDFS_BYTES_READ?site=sanbox=job_1=MAP=0,1
> *History task count in minute*
> http://localhost:9090/rest/mrTasks/historyTaskCount?site=sanbox=job_1=2016-09-12%2005:31:13=2016-09-12%2005:33:10
> *Task suggestion*
> http://localhost:9090/rest/mrTasks/taskSuggestion?site=sanbox_id=job_1_id=job_2



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

[GitHub] incubator-eagle issue #432: EAGLE-538: Add Mapreduce task level apis

2016-09-28 Thread yonzhang

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/432
  
@qingwen220 can you please add good description for this big PR?


---
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-526) aggregation framework for mr history jobs

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-526:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/430
  
@wujinhu can you please add description for people to understand the 
changes.


> aggregation framework for mr history jobs
> -
>
> Key: EAGLE-526
> URL: https://issues.apache.org/jira/browse/EAGLE-526
> Project: Eagle
>  Issue Type: New Feature
>Reporter: wujinhu
>Assignee: wujinhu
>




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

[jira] [Commented] (EAGLE-526) aggregation framework for mr history jobs

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-526:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/429
  
@wujinhu can you please add sufficient description here for people to 
understand what aggregation framework is used for?


> aggregation framework for mr history jobs
> -
>
> Key: EAGLE-526
> URL: https://issues.apache.org/jira/browse/EAGLE-526
> Project: Eagle
>  Issue Type: New Feature
>Reporter: wujinhu
>Assignee: wujinhu
>




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

[GitHub] incubator-eagle issue #430: [EAGLE-526] aggregation framework for history jo...

2016-09-28 Thread yonzhang

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/430
  
@wujinhu can you please add description for people to understand the 
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 issue #429: [EAGLE-526] aggregation framework

2016-09-28 Thread yonzhang

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/429
  
@wujinhu can you please add sufficient description here for people to 
understand what aggregation framework is used for?


---
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 #428: EAGLE-531: Dedup alerts according to state chang...

2016-09-28 Thread yonzhang

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/428
  
@garrettlish is this a duplicated PR? or do we need input more valuable 
description 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-531) Dedup alerts according to state change

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-531:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/428
  
@garrettlish is this a duplicated PR? or do we need input more valuable 
description here?


> Dedup alerts according to state change
> --
>
> Key: EAGLE-531
> URL: https://issues.apache.org/jira/browse/EAGLE-531
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> This is for stateful and stateless logs



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

[jira] [Commented] (EAGLE-522) Implement HOURLY_RULE for Absence Alert.

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-522:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/426
  
@pkuwm this is important PR for absence alert, can you please add detailed 
description for people to learn what are the changes?


> Implement HOURLY_RULE for Absence Alert.
> 
>
> Key: EAGLE-522
> URL: https://issues.apache.org/jira/browse/EAGLE-522
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Huizhi Lu
>Assignee: Huizhi Lu
> Fix For: v0.5.0
>
>
> Absence alert HOURLY_RULE is another use case for customers' needs.



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

[GitHub] incubator-eagle issue #426: [EAGLE-522] Implement HOURLY_RULE for Absence Al...

2016-09-28 Thread yonzhang

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/426
  
@pkuwm this is important PR for absence alert, can you please add detailed 
description for people to learn what are the 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.
---

[jira] [Commented] (EAGLE-531) Dedup alerts according to state change

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-531:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/423
  
@garrettlish can you please add more description to this PR and 
corresponding JIRA ticket EAGLE-531? This PR looks pretty important for people 
to learn alert deduplication.


> Dedup alerts according to state change
> --
>
> Key: EAGLE-531
> URL: https://issues.apache.org/jira/browse/EAGLE-531
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> This is for stateful and stateless logs



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

[GitHub] incubator-eagle issue #423: EAGLE-531: Dedup alerts according to state chang...

2016-09-28 Thread yonzhang

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/423
  
@garrettlish can you please add more description to this PR and 
corresponding JIRA ticket EAGLE-531? This PR looks pretty important for people 
to learn alert deduplication.


---
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-531) Dedup alerts according to state change

2016-09-28 Thread Edward Zhang (JIRA)


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

Edward Zhang updated EAGLE-531:
---
Description: This is for stateful and stateless logs  (was: 
https://wiki.vip.corp.ebay.com/pages/viewpage.action?pageId=361488851)

> Dedup alerts according to state change
> --
>
> Key: EAGLE-531
> URL: https://issues.apache.org/jira/browse/EAGLE-531
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> This is for stateful and stateless logs



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

[jira] [Commented] (EAGLE-524) aggregation framework-job level metrics aggregation

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-524:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/419
  
@wujinhu this is pretty important PR, can you add good description so 
people who are interested in can understand what are those changes for.


> aggregation framework-job level metrics aggregation
> ---
>
> Key: EAGLE-524
> URL: https://issues.apache.org/jira/browse/EAGLE-524
> Project: Eagle
>  Issue Type: New Feature
>Reporter: wujinhu
>Assignee: wujinhu
>




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

[GitHub] incubator-eagle issue #419: [EAGLE-524] aggregation framework-job level metr...

2016-09-28 Thread yonzhang

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/419
  
@wujinhu this is pretty important PR, can you add good description so 
people who are interested in can understand what are those changes for.


---
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 #416: Update spark history job feeder config & refacto...

2016-09-28 Thread yonzhang

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/416
  
@qingwen220 it is a big PR, can you please add description so later on 
people can reference to see what really happened.


---
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-519) No data / gap alert enhancement

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-519:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/413
  
That is fine. I found more details in JIRA
1. no data for an entire stream won't trigger gap alert (use local time & 
batch window) 
2. no data policies definition is too complex, make the nodata offer 
optional settings in stream definition 
3. bolt parallellism will cause multiple alerts in the same time window 
(use loopback)


> No data / gap alert enhancement
> ---
>
> Key: EAGLE-519
> URL: https://issues.apache.org/jira/browse/EAGLE-519
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> 1. no data for an entire stream won't trigger gap alert (use local time & 
> batch window) 
> 2. no data policies definition is too complex, make the nodata offer optional 
> settings in stream definition 
> 3. bolt parallellism will cause multiple alerts in the same time window (use 
> loopback) 



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

[jira] [Commented] (EAGLE-519) No data / gap alert enhancement

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-519:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/413
  
@garrettlish thanks for the PR. Can you please add more description into 
this PR. This PR is pretty important and we believe that people will look at 
this PR to see what really happened.


> No data / gap alert enhancement
> ---
>
> Key: EAGLE-519
> URL: https://issues.apache.org/jira/browse/EAGLE-519
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> 1. no data for an entire stream won't trigger gap alert (use local time & 
> batch window) 
> 2. no data policies definition is too complex, make the nodata offer optional 
> settings in stream definition 
> 3. bolt parallellism will cause multiple alerts in the same time window (use 
> loopback) 



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

[jira] [Commented] (EAGLE-432) Application status monitoring

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-432:
--

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/461
  
I have reviewed the code, basically it should be working, but there might 
be some concurrency issue. But even in this case, I think you can merge this 
PR, and refine them afterwards.


> 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 issue #461: [EAGLE-432] Application status monitoring

2016-09-28 Thread yonzhang

Github user yonzhang commented on the issue:

https://github.com/apache/incubator-eagle/pull/461
  
I have reviewed the code, basically it should be working, but there might 
be some concurrency issue. But even in this case, I think you can merge this 
PR, and refine them afterwards.


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

Check Eagle service running status

2016-09-28 Thread Da Zhou

Hi,

Is there a command that I can run to make sure Eagle is definitely up?

I'm using Eagle-0.4, tried to use "/bin/eagle-service.sh status".
Though it returns "running" but in fact it is not fully started, because
existed topology in Storm could not connect to it.  Then I have to kill the
topology and wait for a few while then submit it.



Regards,
Da

[jira] [Commented] (EAGLE-565) Because of the "type" field when has subqueue ,response of RM REST API doesn‘t match the SchedulerWrapper object

2016-09-28 Thread Jayesh (JIRA)


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

Jayesh commented on EAGLE-565:
--

since this is committed to master, does this make EAGLE-561 invalid ? 

> Because of the "type" field when has subqueue ,response of RM REST API 
> doesn‘t match the SchedulerWrapper object
> 
>
> Key: EAGLE-565
> URL: https://issues.apache.org/jira/browse/EAGLE-565
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
> Environment: hadoop2.6.0-cdh5.4.3
>Reporter: Lingang Deng
>Assignee: Lingang Deng
>Priority: Critical
>
> I got the exception {code:java}Caused by: 
> org.codehaus.jackson.map.JsonMappingException: Can not deserialize instance 
> of java.lang.String out of START_ARRAY token
>  at [Source: java.io.ByteArrayInputStream@1578809b; line: 1, column: 2350] 
> (through reference chain: 
> org.apache.eagle.hadoop.queue.model.scheduler.SchedulerWrapper["scheduler"]->org.apache.eagle.hadoop.queue.model.scheduler.Scheduler["schedulerInfo"]->org.apache.eagle.hadoop.queue.model.scheduler.SchedulerInfo["queues"]->org.apache.eagle.hadoop.queue.model.scheduler.Queues["queue"]->org.apache.eagle.hadoop.queue.model.scheduler.Queue["queues"]->org.apache.eagle.hadoop.queue.model.scheduler.Queues["queue"]->org.apache.eagle.hadoop.queue.model.scheduler.Queue["type"])
> {code} The response of 
> https://some.server.address:50030/ws/v1/cluster/scheduler?anonymous=true, the 
> "type" field maybe return Array, but the right is String, and the field is  
> declared as String in class Queue. Then, I got the root cause, there is a 
> YARN JIRA, [YARN-4785|https://issues.apache.org/jira/browse/YARN-4785].Let me 
> give a case:
> {code:xml}
> {
> "scheduler": {
> "schedulerInfo": {
> "type": "capacityScheduler",
> "capacity": 100,
> "usedCapacity": 0,
> "maxCapacity": 100,
> "queueName": "root",
> "queues": {
> "queue": [
> {
> "type": "capacitySchedulerLeafQueueInfo",
> "capacity": 35,
> "usedCapacity": 0,
> "maxCapacity": 100,
> "absoluteCapacity": 35,
> "absoluteMaxCapacity": 100,
> "absoluteUsedCapacity": 0,
> "numApplications": 0,
> "queueName": "A",
> "state": "RUNNING",
> "resourcesUsed": {
> "memory": 0,
> "vCores": 0
> },
> "hideReservationQueues": false,
> "nodeLabels": [
> "*"
> ],
> "numActiveApplications": 0,
> "numPendingApplications": 0,
> "numContainers": 0,
> "maxApplications": 2,
> "maxApplicationsPerUser": 4,
> "maxActiveApplications": 20,
> "maxActiveApplicationsPerUser": 14,
> "userLimit": 100,
> "users": null,
> "userLimitFactor": 2
> },
> {
> "capacity": 35,
> "usedCapacity": 0,
> "maxCapacity": 35,
> "absoluteCapacity": 35,
> "absoluteMaxCapacity": 35,
> "absoluteUsedCapacity": 0,
> "numApplications": 0,
> "queueName": "B",
> "state": "RUNNING",
> "queues": {
> "queue": [
> {
> "capacity": 37,
> "usedCapacity": 0,
> "maxCapacity": 100,
> "absoluteCapacity": 12.95,
> "absoluteMaxCapacity": 35,
> "absoluteUsedCapacity": 0,
> "numApplications": 0,
> "queueName": "B1",
> "state": "RUNNING",
> "queues": {
> "queue": [
> {
> "type": 
>

[jira] [Commented] (EAGLE-565) Because of the "type" field when has subqueue ,response of RM REST API doesn‘t match the SchedulerWrapper object

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-565:
--

Github user jhsenjaliya commented on the issue:

https://github.com/apache/incubator-eagle/pull/455
  
isnt this is same PR as #451 ?


> Because of the "type" field when has subqueue ,response of RM REST API 
> doesn‘t match the SchedulerWrapper object
> 
>
> Key: EAGLE-565
> URL: https://issues.apache.org/jira/browse/EAGLE-565
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
> Environment: hadoop2.6.0-cdh5.4.3
>Reporter: Lingang Deng
>Assignee: Lingang Deng
>Priority: Critical
>
> I got the exception {code:java}Caused by: 
> org.codehaus.jackson.map.JsonMappingException: Can not deserialize instance 
> of java.lang.String out of START_ARRAY token
>  at [Source: java.io.ByteArrayInputStream@1578809b; line: 1, column: 2350] 
> (through reference chain: 
> org.apache.eagle.hadoop.queue.model.scheduler.SchedulerWrapper["scheduler"]->org.apache.eagle.hadoop.queue.model.scheduler.Scheduler["schedulerInfo"]->org.apache.eagle.hadoop.queue.model.scheduler.SchedulerInfo["queues"]->org.apache.eagle.hadoop.queue.model.scheduler.Queues["queue"]->org.apache.eagle.hadoop.queue.model.scheduler.Queue["queues"]->org.apache.eagle.hadoop.queue.model.scheduler.Queues["queue"]->org.apache.eagle.hadoop.queue.model.scheduler.Queue["type"])
> {code} The response of 
> https://some.server.address:50030/ws/v1/cluster/scheduler?anonymous=true, the 
> "type" field maybe return Array, but the right is String, and the field is  
> declared as String in class Queue. Then, I got the root cause, there is a 
> YARN JIRA, [YARN-4785|https://issues.apache.org/jira/browse/YARN-4785].Let me 
> give a case:
> {code:xml}
> {
> "scheduler": {
> "schedulerInfo": {
> "type": "capacityScheduler",
> "capacity": 100,
> "usedCapacity": 0,
> "maxCapacity": 100,
> "queueName": "root",
> "queues": {
> "queue": [
> {
> "type": "capacitySchedulerLeafQueueInfo",
> "capacity": 35,
> "usedCapacity": 0,
> "maxCapacity": 100,
> "absoluteCapacity": 35,
> "absoluteMaxCapacity": 100,
> "absoluteUsedCapacity": 0,
> "numApplications": 0,
> "queueName": "A",
> "state": "RUNNING",
> "resourcesUsed": {
> "memory": 0,
> "vCores": 0
> },
> "hideReservationQueues": false,
> "nodeLabels": [
> "*"
> ],
> "numActiveApplications": 0,
> "numPendingApplications": 0,
> "numContainers": 0,
> "maxApplications": 2,
> "maxApplicationsPerUser": 4,
> "maxActiveApplications": 20,
> "maxActiveApplicationsPerUser": 14,
> "userLimit": 100,
> "users": null,
> "userLimitFactor": 2
> },
> {
> "capacity": 35,
> "usedCapacity": 0,
> "maxCapacity": 35,
> "absoluteCapacity": 35,
> "absoluteMaxCapacity": 35,
> "absoluteUsedCapacity": 0,
> "numApplications": 0,
> "queueName": "B",
> "state": "RUNNING",
> "queues": {
> "queue": [
> {
> "capacity": 37,
> "usedCapacity": 0,
> "maxCapacity": 100,
> "absoluteCapacity": 12.95,
> "absoluteMaxCapacity": 35,
> "absoluteUsedCapacity": 0,
> "numApplications": 0,
> "queueName": "B1",
> "state": "RUNNING",
> "queues": {
> "queue": [
>

[GitHub] incubator-eagle issue #455: EAGLE-565 Because of the "type" field when has s...

2016-09-28 Thread jhsenjaliya

Github user jhsenjaliya commented on the issue:

https://github.com/apache/incubator-eagle/pull/455
  
isnt this is same PR as #451 ?


---
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-575) Refactor StaticWebApplication to StaticApplication to support both web/static application

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-575:
--

GitHub user haoch opened a pull request:

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

EAGLE-575 Refactor StaticWebApplication to StaticApplication

* 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

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

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

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

https://github.com/apache/incubator-eagle/pull/464.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 #464


commit f79b18061d794336593d725ca464ff677804988e
Author: Hao Chen 
Date:   2016-09-28T05:44:14Z

EAGLE-575 Refactor StaticWebApplication to StaticApplication to support 
both web/static application

* 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)

[GitHub] incubator-eagle pull request #464: EAGLE-575 Refactor StaticWebApplication t...

2016-09-28 Thread haoch

GitHub user haoch opened a pull request:

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

EAGLE-575 Refactor StaticWebApplication to StaticApplication

* 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

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

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

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

https://github.com/apache/incubator-eagle/pull/464.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 #464


commit f79b18061d794336593d725ca464ff677804988e
Author: Hao Chen 
Date:   2016-09-28T05:44:14Z

EAGLE-575 Refactor StaticWebApplication to StaticApplication to support 
both web/static application

* 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




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

[EAGLE BUILD FAILED] incubator-eagle-main failed on build #144

2016-09-28 Thread Apache Jenkins Server

The Apache Jenkins build system has built incubator-eagle-main (build #144) 
Status: Still Failing Check console output at 
https://builds.apache.org/job/incubator-eagle-main/144/ to view the 
results. Test Report is at: Test Result

[jira] [Commented] (EAGLE-576) Dedup enhancements

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-576:
--

Github user asfgit closed the pull request at:

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


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

[GitHub] incubator-eagle pull request #463: EAGLE-576: change dedup db store to per p...

2016-09-28 Thread asfgit

Github user asfgit closed the pull request at:

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


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

[EAGLE BUILD FAILED] incubator-eagle-main failed on build #143

2016-09-28 Thread Apache Jenkins Server

The Apache Jenkins build system has built incubator-eagle-main (build #143) 
Status: Still Failing Check console output at 
https://builds.apache.org/job/incubator-eagle-main/143/ to view the 
results. Test Report is at: Test Result

[jira] [Commented] (EAGLE-576) Dedup enhancements

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-576:
--

GitHub user garrettlish opened a pull request:

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

EAGLE-576: change dedup db store to per publishment rather than global



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/463.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 #463


commit 167434a00b0fc660ab420751a1828b0c18c9cb06
Author: Xiancheng Li 
Date:   2016-09-28T10:31:55Z

EAGLE-576: change dedup db store to per publishment rather than global




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

[GitHub] incubator-eagle pull request #463: EAGLE-576: change dedup db store to per p...

2016-09-28 Thread garrettlish

GitHub user garrettlish opened a pull request:

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

EAGLE-576: change dedup db store to per publishment rather than global



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/463.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 #463


commit 167434a00b0fc660ab420751a1828b0c18c9cb06
Author: Xiancheng Li 
Date:   2016-09-28T10:31:55Z

EAGLE-576: change dedup db store to per publishment rather than global




---
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-565) Because of the "type" field when has subqueue ,response of RM REST API doesn‘t match the SchedulerWrapper object

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-565:
--

Github user asfgit closed the pull request at:

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


> Because of the "type" field when has subqueue ,response of RM REST API 
> doesn‘t match the SchedulerWrapper object
> 
>
> Key: EAGLE-565
> URL: https://issues.apache.org/jira/browse/EAGLE-565
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
> Environment: hadoop2.6.0-cdh5.4.3
>Reporter: Lingang Deng
>Assignee: Lingang Deng
>Priority: Critical
>
> I got the exception {code:java}Caused by: 
> org.codehaus.jackson.map.JsonMappingException: Can not deserialize instance 
> of java.lang.String out of START_ARRAY token
>  at [Source: java.io.ByteArrayInputStream@1578809b; line: 1, column: 2350] 
> (through reference chain: 
> org.apache.eagle.hadoop.queue.model.scheduler.SchedulerWrapper["scheduler"]->org.apache.eagle.hadoop.queue.model.scheduler.Scheduler["schedulerInfo"]->org.apache.eagle.hadoop.queue.model.scheduler.SchedulerInfo["queues"]->org.apache.eagle.hadoop.queue.model.scheduler.Queues["queue"]->org.apache.eagle.hadoop.queue.model.scheduler.Queue["queues"]->org.apache.eagle.hadoop.queue.model.scheduler.Queues["queue"]->org.apache.eagle.hadoop.queue.model.scheduler.Queue["type"])
> {code} The response of 
> https://some.server.address:50030/ws/v1/cluster/scheduler?anonymous=true, the 
> "type" field maybe return Array, but the right is String, and the field is  
> declared as String in class Queue. Then, I got the root cause, there is a 
> YARN JIRA, [YARN-4785|https://issues.apache.org/jira/browse/YARN-4785].Let me 
> give a case:
> {code:xml}
> {
> "scheduler": {
> "schedulerInfo": {
> "type": "capacityScheduler",
> "capacity": 100,
> "usedCapacity": 0,
> "maxCapacity": 100,
> "queueName": "root",
> "queues": {
> "queue": [
> {
> "type": "capacitySchedulerLeafQueueInfo",
> "capacity": 35,
> "usedCapacity": 0,
> "maxCapacity": 100,
> "absoluteCapacity": 35,
> "absoluteMaxCapacity": 100,
> "absoluteUsedCapacity": 0,
> "numApplications": 0,
> "queueName": "A",
> "state": "RUNNING",
> "resourcesUsed": {
> "memory": 0,
> "vCores": 0
> },
> "hideReservationQueues": false,
> "nodeLabels": [
> "*"
> ],
> "numActiveApplications": 0,
> "numPendingApplications": 0,
> "numContainers": 0,
> "maxApplications": 2,
> "maxApplicationsPerUser": 4,
> "maxActiveApplications": 20,
> "maxActiveApplicationsPerUser": 14,
> "userLimit": 100,
> "users": null,
> "userLimitFactor": 2
> },
> {
> "capacity": 35,
> "usedCapacity": 0,
> "maxCapacity": 35,
> "absoluteCapacity": 35,
> "absoluteMaxCapacity": 35,
> "absoluteUsedCapacity": 0,
> "numApplications": 0,
> "queueName": "B",
> "state": "RUNNING",
> "queues": {
> "queue": [
> {
> "capacity": 37,
> "usedCapacity": 0,
> "maxCapacity": 100,
> "absoluteCapacity": 12.95,
> "absoluteMaxCapacity": 35,
> "absoluteUsedCapacity": 0,
> "numApplications": 0,
> "queueName": "B1",
> "state": "RUNNING",
> "queues": {
> "queue": [
> {
>

[GitHub] incubator-eagle pull request #455: EAGLE-565 Because of the "type" field whe...

2016-09-28 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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-565) Because of the "type" field when has subqueue ,response of RM REST API doesn‘t match the SchedulerWrapper object

2016-09-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-565:
--

Github user qingwen220 commented on the issue:

https://github.com/apache/incubator-eagle/pull/455
  
As 'type' field is not a must to have for Eagle, it is ok to remove it. I 
will merge this pr


> Because of the "type" field when has subqueue ,response of RM REST API 
> doesn‘t match the SchedulerWrapper object
> 
>
> Key: EAGLE-565
> URL: https://issues.apache.org/jira/browse/EAGLE-565
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.4.0
> Environment: hadoop2.6.0-cdh5.4.3
>Reporter: Lingang Deng
>Assignee: Lingang Deng
>Priority: Critical
>
> I got the exception {code:java}Caused by: 
> org.codehaus.jackson.map.JsonMappingException: Can not deserialize instance 
> of java.lang.String out of START_ARRAY token
>  at [Source: java.io.ByteArrayInputStream@1578809b; line: 1, column: 2350] 
> (through reference chain: 
> org.apache.eagle.hadoop.queue.model.scheduler.SchedulerWrapper["scheduler"]->org.apache.eagle.hadoop.queue.model.scheduler.Scheduler["schedulerInfo"]->org.apache.eagle.hadoop.queue.model.scheduler.SchedulerInfo["queues"]->org.apache.eagle.hadoop.queue.model.scheduler.Queues["queue"]->org.apache.eagle.hadoop.queue.model.scheduler.Queue["queues"]->org.apache.eagle.hadoop.queue.model.scheduler.Queues["queue"]->org.apache.eagle.hadoop.queue.model.scheduler.Queue["type"])
> {code} The response of 
> https://some.server.address:50030/ws/v1/cluster/scheduler?anonymous=true, the 
> "type" field maybe return Array, but the right is String, and the field is  
> declared as String in class Queue. Then, I got the root cause, there is a 
> YARN JIRA, [YARN-4785|https://issues.apache.org/jira/browse/YARN-4785].Let me 
> give a case:
> {code:xml}
> {
> "scheduler": {
> "schedulerInfo": {
> "type": "capacityScheduler",
> "capacity": 100,
> "usedCapacity": 0,
> "maxCapacity": 100,
> "queueName": "root",
> "queues": {
> "queue": [
> {
> "type": "capacitySchedulerLeafQueueInfo",
> "capacity": 35,
> "usedCapacity": 0,
> "maxCapacity": 100,
> "absoluteCapacity": 35,
> "absoluteMaxCapacity": 100,
> "absoluteUsedCapacity": 0,
> "numApplications": 0,
> "queueName": "A",
> "state": "RUNNING",
> "resourcesUsed": {
> "memory": 0,
> "vCores": 0
> },
> "hideReservationQueues": false,
> "nodeLabels": [
> "*"
> ],
> "numActiveApplications": 0,
> "numPendingApplications": 0,
> "numContainers": 0,
> "maxApplications": 2,
> "maxApplicationsPerUser": 4,
> "maxActiveApplications": 20,
> "maxActiveApplicationsPerUser": 14,
> "userLimit": 100,
> "users": null,
> "userLimitFactor": 2
> },
> {
> "capacity": 35,
> "usedCapacity": 0,
> "maxCapacity": 35,
> "absoluteCapacity": 35,
> "absoluteMaxCapacity": 35,
> "absoluteUsedCapacity": 0,
> "numApplications": 0,
> "queueName": "B",
> "state": "RUNNING",
> "queues": {
> "queue": [
> {
> "capacity": 37,
> "usedCapacity": 0,
> "maxCapacity": 100,
> "absoluteCapacity": 12.95,
> "absoluteMaxCapacity": 35,
> "absoluteUsedCapacity": 0,
> "numApplications": 0,
> "queueName": "B1",
> "state": "RUNNING",
> "queues": {
>

[GitHub] incubator-eagle pull request #459: [Minor] Update History Job Counting API

2016-09-28 Thread asfgit

Github user asfgit closed the pull request at:

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


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

Re: [EAGLE BUILD FAILED] incubator-eagle-main failed on build #142

2016-09-28 Thread Michael Wu

Guys,

The job is failing for running on slaves that have wrong node.js version.
I've opened a ticket for INFRA team:
https://issues.apache.org/jira/browse/INFRA-12669.

Once it's solved, I'll verify the building result.

Just let you know it. Thanks.

Michael

On Wed, Sep 28, 2016 at 4:39 PM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> The Apache Jenkins build system has built incubator-eagle-main (build #142)
> Status: Still Failing Check console output at
> https://builds.apache.org/job/incubator-eagle-main/142/ to view the
> results. Test Report is at: Test Result
>

[EAGLE BUILD FAILED] incubator-eagle-main failed on build #142

2016-09-28 Thread Apache Jenkins Server

The Apache Jenkins build system has built incubator-eagle-main (build #142) 
Status: Still Failing Check console output at 
https://builds.apache.org/job/incubator-eagle-main/142/ to view the 
results. Test Report is at: Test Result

[GitHub] incubator-eagle pull request #462: EAGLE-576: dedup enhancements

2016-09-28 Thread asfgit

Github user asfgit closed the pull request at:

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


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

[EAGLE BUILD FAILED] incubator-eagle-main failed on build #141

2016-09-28 Thread Apache Jenkins Server

The Apache Jenkins build system has built incubator-eagle-main (build #141) 
Status: Failure Check console output at 
https://builds.apache.org/job/incubator-eagle-main/141/ to view the 
results. Test Report is at: Test Result

[jira] [Created] (EAGLE-577) UI policy management

2016-09-28 Thread Jilin, Jiang (JIRA)

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

2016-09-28 Thread Jilin, Jiang (JIRA)


 [ 
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

2016-09-28 Thread garrettlish

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

2016-09-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/EAGLE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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

2016-09-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/EAGLE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)

[jira] [Updated] (EAGLE-576) Dedup enhancements

2016-09-28 Thread Garrett Li (JIRA)


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

63 matches

Mail list logo