[jira] [Commented] (EAGLE-550) Add Alert publish implementation for Slack

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

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

ASF GitHub Bot commented on EAGLE-550:
--

Github user mizeng commented on the issue:

https://github.com/apache/incubator-eagle/pull/442
  
+1


> 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-21 Thread mizeng 
Github user mizeng commented on the issue:

https://github.com/apache/incubator-eagle/pull/442
  
+1


---
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-564) pack mr history/running feeder in one topology and bugs fix

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

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

ASF GitHub Bot commented on EAGLE-564:
--

GitHub user wujinhu opened a pull request:

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

[EAGLE-564] pack mr history/running feeder in one topology and bugs fix

https://issues.apache.org/jira/browse/EAGLE-564

Pack MR history/Running feeder in the final topology by using 
topology-assembly. 
Changes:
1. remove useless configure
2. add application provider to topology assembly spi
Bug fix:
1. Storm configure(workers/timeout...) does not overrided by customer 
defined configure.
2. When install an application, user may not set jarPath, in this case, we 
need to dynamic load, otherwise, use the jarPath that user provides.

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

$ git pull https://github.com/wujinhu/incubator-eagle deploy

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

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


commit 15fe613f3426cb726c8dfaae3460f0d74ceac15f
Author: wujinhu 
Date:   2016-09-22T05:08:14Z

pack mr history/running feeder in one topology and bugs fix




> pack mr history/running feeder in one topology and bugs fix
> ---
>
> Key: EAGLE-564
> URL: https://issues.apache.org/jira/browse/EAGLE-564
> Project: Eagle
>  Issue Type: Improvement
>Reporter: wujinhu
>Assignee: wujinhu
>
> Pack MR history/Running feeder in the final topology by using 
> topology-assembly. 
> Changes:
> 1. remove useless configure
> 2. add application provider to topology assembly spi
> Bug fix:
> 1. Storm configure(workers/timeout...) does not overrided by customer defined 
> configure.
> 2. When install an application, user may not set jarPath, in this case, we 
> need to dynamic load, otherwise, use the jarPath that user provides.



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

[GitHub] incubator-eagle pull request #448: [EAGLE-564] pack mr history/running feede...

2016-09-21 Thread wujinhu 
GitHub user wujinhu opened a pull request:

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

[EAGLE-564] pack mr history/running feeder in one topology and bugs fix

https://issues.apache.org/jira/browse/EAGLE-564

Pack MR history/Running feeder in the final topology by using 
topology-assembly. 
Changes:
1. remove useless configure
2. add application provider to topology assembly spi
Bug fix:
1. Storm configure(workers/timeout...) does not overrided by customer 
defined configure.
2. When install an application, user may not set jarPath, in this case, we 
need to dynamic load, otherwise, use the jarPath that user provides.

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

$ git pull https://github.com/wujinhu/incubator-eagle deploy

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

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


commit 15fe613f3426cb726c8dfaae3460f0d74ceac15f
Author: wujinhu 
Date:   2016-09-22T05:08:14Z

pack mr history/running feeder in one topology and bugs fix




---
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-564) pack mr history/running feeder in one topology and bugs fix

2016-09-21 Thread wujinhu (JIRA) 
wujinhu created EAGLE-564:
-

 Summary: pack mr history/running feeder in one topology and bugs 
fix
 Key: EAGLE-564
 URL: https://issues.apache.org/jira/browse/EAGLE-564
 Project: Eagle
  Issue Type: Improvement
Reporter: wujinhu
Assignee: wujinhu


Pack MR history/Running feeder in the final topology by using 
topology-assembly. 
Changes:
1. remove useless configure
2. add application provider to topology assembly spi
Bug fix:
1. Storm configure(workers/timeout...) does not overrided by customer defined 
configure.
2. When install an application, user may not set jarPath, in this case, we need 
to dynamic load, otherwise, use the jarPath that user provides.



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

Re: Can You Give Me More Sample Data to Be Used for Training

2016-09-21 Thread Edward Zhang 
Hi Xin Wu,

Sorry for late reply. Thanks for your interest in user profile but it looks
very hard to provide more sample data. Sometimes you need production data
to simulate your test.

But if you need sample data, probably you can write program to generate
random ip, user, read/write cmd etc and do some fault injection. Anyway its
purpose is to find out the obvious difference between training data and
test data.

2015-04-24 12:49:16,145 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfosrc=/tmp
dst=null   perm=null  proto=rpc
2015-04-24 12:49:16,192 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfo
src=/user/ambari-qadst=null   perm=null  proto=rpc
2015-04-24 12:49:20,518 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfosrc=/tmp
dst=null   perm=null  proto=rpc
2015-04-24 12:49:20,570 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfo
src=/user/ambari-qadst=null   perm=null  proto=rpc
2015-04-24 12:49:20,587 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfosrc=/
dst=null   perm=null  proto=rpc
2015-04-24 12:49:20,664 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=mkdirs src=/tmp   dst=null
perm=hdfs:hdfs:rwxr-xr-x   proto=rpc
2015-04-24 12:49:20,677 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfosrc=/user
dst=null   perm=null  proto=rpc
2015-04-24 12:49:20,686 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=mkdirs src=/user/ambari-qa
 dst=null   perm=hdfs:hdfs:rwxr-xr-x   proto=rpc
2015-04-24 12:49:24,828 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfosrc=/tmp
dst=null   perm=null  proto=rpc
2015-04-24 12:49:24,915 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=setPermission  src=/tmp
dst=null   perm=hdfs:hdfs:rwxrwxrwx   proto=rpc
2015-04-24 12:49:29,375 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfo
src=/user/ambari-qadst=null   perm=null  proto=rpc
2015-04-24 12:49:29,453 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=setPermission
src=/user/ambari-qadst=null   perm=hdfs:hdfs:rwxrwx---   proto=rpc
2015-04-24 12:49:33,542 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfosrc=/tmp
dst=null   perm=null  proto=rpc
2015-04-24 12:49:37,844 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfo
src=/user/ambari-qadst=null   perm=null  proto=rpc
2015-04-24 12:49:37,929 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=setOwner
src=/user/ambari-qadst=null   perm=ambari-qa:hdfs:rwxrwx---
proto=rpc
2015-04-24 12:51:31,798 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfo
src=/apps/hbase/data   dst=null   perm=null  proto=rpc
2015-04-24 12:51:31,863 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfo
src=/apps/hbase/stagingdst=null   perm=null  proto=rpc


Thanks

Edward


On Sat, Sep 17, 2016 at 7:41 PM, 辛武  wrote:

> Dear Eagle Development Team:
> My name is Xin Wu, a college student of Peking University, and I am
> writing in the hope of your assistance to provide more sample data to me.
> First and foremost I know Eagle is the first activity monitoring
> system on the Hadoop-ecosystem for the detection of intrusion-related
> activities using behavior-based profiles of users. I am particularly
> interested in the project of Eagle and its ideas, at the same time, I also
> read the paper, Eagle: User Profile-based Anomaly Detection for Securing
> Hadoop Clusters. And I want to learn more, I need more sample data for
> research. Will you be able to supply more data to me?
> Looking forward to a prompt reply from you.
>
>  Sincerely yours,
>Xin Wu
>

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

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

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

ASF GitHub Bot commented on EAGLE-522:
--

Github user pkuwm commented on the issue:

https://github.com/apache/incubator-eagle/pull/426
  
@haoch Done.


> 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-21 Thread pkuwm 
Github user pkuwm commented on the issue:

https://github.com/apache/incubator-eagle/pull/426
  
@haoch Done.


---
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 #130

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

RE: MySql Connection properties in eagle-service.conf

2016-09-21 Thread Jaspaul Chahal 
Hi Ed,

Thanks, I am using 0.4 .  The connection is successful using ? and then 
connection parameters. 

Will try more connection parameters those I wanted to try and will keep you 
posted in case I find any issue.

Thanks again!

Regards,
Jaspaul Chahal

-Original Message-
From: Edward Zhang [mailto:yonzhang2...@apache.org] 
Sent: Wednesday, September 21, 2016 11:38 AM
To: dev@eagle.incubator.apache.org
Cc: Subra Ramesh 
Subject: Re: MySql Connection properties in eagle-service.conf

In order not to block your current work, maybe you can try to config 
storage-connection-url to append extra connection properties, for example the 
following

url="jdbc:mysql://localhost/eagle_db?useUnicode=yescharacterEncoding=utf8"


On Wed, Sep 21, 2016 at 11:26 AM, Edward Zhang 
wrote:

> This connection-props is not applied in the code, but it should be 
> appended to end of connection string. I am looking into the place 
> where we can hook this configuration. Are you using Eagle 0.3?
>
> Thanks
> Edward
>
> On Wed, Sep 21, 2016 at 10:51 AM, Jaspaul Chahal 
> 
> wrote:
>
>> Anyone from Apache Eagle team please?
>>
>> Regards,
>> Jaspaul
>>
>> From: Jaspaul Chahal
>> Sent: Tuesday, September 20, 2016 5:26 PM
>> To: dev@eagle.incubator.apache.org
>> Cc: Subra Ramesh (sram...@dataguise.com) 
>> Subject: MySql Connection properties in eagle-service.conf
>>
>> Hello Team,
>>
>> It's regarding MySql as backend repo fro Apache Eagle.
>>
>> In eagle-service.conf file for MySql we have the following property:
>>storage-connection-props="encoding=UTF-8"
>>
>> But, I couldn't find the code using this property for the connection 
>> creation in  
>> TorqueConnectionManagerImpl.buildConfiguration(ConnectionConfig
>> config) .
>>
>> Can someone please point me to the code where we are using this 
>> connection properties for the connection. I need to pass some extra 
>> connection parameters for MySql.
>>
>> Thanks in advance!
>>
>> Regards,
>> Jaspaul Chahal
>>
>
>

Re: MySql Connection properties in eagle-service.conf

2016-09-21 Thread Edward Zhang 
In order not to block your current work, maybe you can try to config
storage-connection-url
to append extra connection properties, for example the following

url="jdbc:mysql://localhost/eagle_db?useUnicode=yescharacterEncoding=utf8"


On Wed, Sep 21, 2016 at 11:26 AM, Edward Zhang 
wrote:

> This connection-props is not applied in the code, but it should be
> appended to end of connection string. I am looking into the place where we
> can hook this configuration. Are you using Eagle 0.3?
>
> Thanks
> Edward
>
> On Wed, Sep 21, 2016 at 10:51 AM, Jaspaul Chahal 
> wrote:
>
>> Anyone from Apache Eagle team please?
>>
>> Regards,
>> Jaspaul
>>
>> From: Jaspaul Chahal
>> Sent: Tuesday, September 20, 2016 5:26 PM
>> To: dev@eagle.incubator.apache.org
>> Cc: Subra Ramesh (sram...@dataguise.com) 
>> Subject: MySql Connection properties in eagle-service.conf
>>
>> Hello Team,
>>
>> It's regarding MySql as backend repo fro Apache Eagle.
>>
>> In eagle-service.conf file for MySql we have the following property:
>>storage-connection-props="encoding=UTF-8"
>>
>> But, I couldn't find the code using this property for the connection
>> creation in  TorqueConnectionManagerImpl.buildConfiguration(ConnectionConfig
>> config) .
>>
>> Can someone please point me to the code where we are using this
>> connection properties for the connection. I need to pass some extra
>> connection parameters for MySql.
>>
>> Thanks in advance!
>>
>> Regards,
>> Jaspaul Chahal
>>
>
>

Re: MySql Connection properties in eagle-service.conf

2016-09-21 Thread Edward Zhang 
This connection-props is not applied in the code, but it should be appended
to end of connection string. I am looking into the place where we can hook
this configuration. Are you using Eagle 0.3?

Thanks
Edward

On Wed, Sep 21, 2016 at 10:51 AM, Jaspaul Chahal 
wrote:

> Anyone from Apache Eagle team please?
>
> Regards,
> Jaspaul
>
> From: Jaspaul Chahal
> Sent: Tuesday, September 20, 2016 5:26 PM
> To: dev@eagle.incubator.apache.org
> Cc: Subra Ramesh (sram...@dataguise.com) 
> Subject: MySql Connection properties in eagle-service.conf
>
> Hello Team,
>
> It's regarding MySql as backend repo fro Apache Eagle.
>
> In eagle-service.conf file for MySql we have the following property:
>storage-connection-props="encoding=UTF-8"
>
> But, I couldn't find the code using this property for the connection
> creation in  TorqueConnectionManagerImpl.buildConfiguration(ConnectionConfig
> config) .
>
> Can someone please point me to the code where we are using this connection
> properties for the connection. I need to pass some extra connection
> parameters for MySql.
>
> Thanks in advance!
>
> Regards,
> Jaspaul Chahal
>

RE: MySql Connection properties in eagle-service.conf

2016-09-21 Thread Jaspaul Chahal 
Anyone from Apache Eagle team please?

Regards,
Jaspaul

From: Jaspaul Chahal
Sent: Tuesday, September 20, 2016 5:26 PM
To: dev@eagle.incubator.apache.org
Cc: Subra Ramesh (sram...@dataguise.com) 
Subject: MySql Connection properties in eagle-service.conf

Hello Team,

It's regarding MySql as backend repo fro Apache Eagle.

In eagle-service.conf file for MySql we have the following property:
   storage-connection-props="encoding=UTF-8"

But, I couldn't find the code using this property for the connection creation 
in  TorqueConnectionManagerImpl.buildConfiguration(ConnectionConfig config) .

Can someone please point me to the code where we are using this connection 
properties for the connection. I need to pass some extra connection parameters 
for MySql.

Thanks in advance!

Regards,
Jaspaul Chahal

[jira] [Created] (EAGLE-563) refactor Hadoop quieue feeder using application framework

2016-09-21 Thread Zhao, Qingwen (JIRA) 
Zhao, Qingwen created EAGLE-563:
---

 Summary: refactor Hadoop quieue feeder using application framework
 Key: EAGLE-563
 URL: https://issues.apache.org/jira/browse/EAGLE-563
 Project: Eagle
  Issue Type: Improvement
Reporter: Zhao, Qingwen
Assignee: Zhao, Qingwen






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

[jira] [Created] (EAGLE-562) Add a new metric totalVirtualCores in Hadoop queue feeder

2016-09-21 Thread Zhao, Qingwen (JIRA) 
Zhao, Qingwen created EAGLE-562:
---

 Summary: Add a new metric totalVirtualCores in Hadoop queue feeder
 Key: EAGLE-562
 URL: https://issues.apache.org/jira/browse/EAGLE-562
 Project: Eagle
  Issue Type: Improvement
Reporter: Zhao, Qingwen
Assignee: Zhao, Qingwen


Since Hadoop 2.7, there is a new metric 'totalVirtualCores' in RM cluster 
metrics API.




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

[jira] [Created] (EAGLE-561) JsonMappingException in Hadoop queue feeder

2016-09-21 Thread Zhao, Qingwen (JIRA) 
Zhao, Qingwen created EAGLE-561:
---

 Summary: JsonMappingException in Hadoop queue feeder
 Key: EAGLE-561
 URL: https://issues.apache.org/jira/browse/EAGLE-561
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Zhao, Qingwen
Assignee: Zhao, Qingwen
 Fix For: v0.5.0


This exception is caused by a yarn rest api bug: 
https://issues.apache.org/jira/browse/YARN-4785

the "type" field for LeafQueueInfo in response of RM REST API  has inconsistent 
value type ( String and Array ) . While String type is expected



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

[jira] [Updated] (EAGLE-560) Retry embedded zookeeper port by port +1 when conflicts

2016-09-21 Thread Hao Chen (JIRA) 

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

Hao Chen updated EAGLE-560:
---
Description: Retry embedded zookeeper port by port +1 when conflicts

> Retry embedded zookeeper port by port +1 when conflicts
> ---
>
> Key: EAGLE-560
> URL: https://issues.apache.org/jira/browse/EAGLE-560
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Retry embedded zookeeper port by port +1 when conflicts



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

[jira] [Resolved] (EAGLE-560) Retry embedded zookeeper port by port +1 when conflicts

2016-09-21 Thread Hao Chen (JIRA) 

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

Hao Chen resolved EAGLE-560.

Resolution: Fixed

> Retry embedded zookeeper port by port +1 when conflicts
> ---
>
> Key: EAGLE-560
> URL: https://issues.apache.org/jira/browse/EAGLE-560
> 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)

[GitHub] incubator-eagle pull request #447: EAGLE-560 Retry embedded zookeeper port b...

2016-09-21 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
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-560) Retry embedded zookeeper port by port +1 when conflicts

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

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

ASF GitHub Bot commented on EAGLE-560:
--

Github user asfgit closed the pull request at:

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


> Retry embedded zookeeper port by port +1 when conflicts
> ---
>
> Key: EAGLE-560
> URL: https://issues.apache.org/jira/browse/EAGLE-560
> 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-560) Retry embedded zookeeper port by port +1 when conflicts

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

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

ASF GitHub Bot commented on EAGLE-560:
--

GitHub user haoch opened a pull request:

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

EAGLE-560 Retry embedded zookeeper port by port +1 when conflicts

https://issues.apache.org/jira/browse/EAGLE-560

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

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

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

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


commit 336f5463d617daf214629315668d73e6154f5fc5
Author: Hao Chen 
Date:   2016-09-21T11:05:31Z

Retry embedded zookeeper port by port +1 when conflicts




> Retry embedded zookeeper port by port +1 when conflicts
> ---
>
> Key: EAGLE-560
> URL: https://issues.apache.org/jira/browse/EAGLE-560
> 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)

[GitHub] incubator-eagle pull request #447: EAGLE-560 Retry embedded zookeeper port b...

2016-09-21 Thread haoch 
GitHub user haoch opened a pull request:

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

EAGLE-560 Retry embedded zookeeper port by port +1 when conflicts

https://issues.apache.org/jira/browse/EAGLE-560

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

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

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

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


commit 336f5463d617daf214629315668d73e6154f5fc5
Author: Hao Chen 
Date:   2016-09-21T11:05:31Z

Retry embedded zookeeper port by port +1 when conflicts




---
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-560) Retry embedded zookeeper port by port +1 when conflicts

2016-09-21 Thread Hao Chen (JIRA) 
Hao Chen created EAGLE-560:
--

 Summary: Retry embedded zookeeper port by port +1 when conflicts
 Key: EAGLE-560
 URL: https://issues.apache.org/jira/browse/EAGLE-560
 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)

[GitHub] incubator-eagle pull request #446: [EAGLE-559] Fix TestServiceAppWithZk test...

2016-09-21 Thread haoch 
GitHub user haoch opened a pull request:

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

[EAGLE-559] Fix TestServiceAppWithZk test cause failing due to port conflict

https://issues.apache.org/jira/browse/EAGLE-559

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

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

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

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


commit 789b3d58d4ea738ef60cf7de9048cde03240
Author: Hao Chen 
Date:   2016-09-21T10:10:01Z

Fix TestServiceAppWithZk test cause failing due to port conflict




---
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-559) Fix TestServiceAppWithZk test cause failing due to port conflict

2016-09-21 Thread Hao Chen (JIRA) 

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

Hao Chen updated EAGLE-559:
---
Labels: alert-engine alert-service  (was: )

> Fix TestServiceAppWithZk test cause failing due to port conflict
> 
>
> Key: EAGLE-559
> URL: https://issues.apache.org/jira/browse/EAGLE-559
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
>  Labels: alert-engine, alert-service
> Fix For: v0.5.0
>
>
> {code}
> Regression
> com.apache.eagle.service.app.TestServiceAppWithZk.testMain
> Failing for the past 1 build (Since Failed#127 )
> Took 5.7 sec.
> Error Message
> java.net.BindException: Address already in use
> Stacktrace
> java.lang.RuntimeException: java.net.BindException: Address already in use
>   at 
> org.eclipse.jetty.setuid.SetUIDListener.lifeCycleStarting(SetUIDListener.java:213)
>   at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.setStarting(AbstractLifeCycle.java:187)
>   at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
>   at io.dropwizard.cli.ServerCommand.run(ServerCommand.java:43)
>   at io.dropwizard.cli.EnvironmentCommand.run(EnvironmentCommand.java:43)
>   at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:76)
>   at io.dropwizard.cli.Cli.run(Cli.java:70)
>   at io.dropwizard.Application.run(Application.java:72)
>   at 
> com.apache.eagle.service.app.TestServiceAppWithZk.setUp(TestServiceAppWithZk.java:69)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59)
>   at 
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:120)
>   at 
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:103)
>   at org.apache.maven.surefire.Surefire.run(Surefire.java:169)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350)
>   at 
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021)
> Caused by: java.net.BindException: Address already in use
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Net.java:433)
>   at sun.nio.ch.Net.bind(Net.java:425)
>   at 
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
>   at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>   at 
> org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:264)
>   at 
> org.eclipse.jetty.setuid.SetUIDListener.lifeCycleStarting(SetUIDListener.java:200)
>   ... 36 more
> {code}



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

[jira] [Created] (EAGLE-559) Fix TestServiceAppWithZk test cause failing due to port conflict

2016-09-21 Thread Hao Chen (JIRA) 
Hao Chen created EAGLE-559:
--

 Summary: Fix TestServiceAppWithZk test cause failing due to port 
conflict
 Key: EAGLE-559
 URL: https://issues.apache.org/jira/browse/EAGLE-559
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.5.0


{code}
Regression

com.apache.eagle.service.app.TestServiceAppWithZk.testMain

Failing for the past 1 build (Since Failed#127 )
Took 5.7 sec.
Error Message

java.net.BindException: Address already in use
Stacktrace

java.lang.RuntimeException: java.net.BindException: Address already in use
at 
org.eclipse.jetty.setuid.SetUIDListener.lifeCycleStarting(SetUIDListener.java:213)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.setStarting(AbstractLifeCycle.java:187)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at io.dropwizard.cli.ServerCommand.run(ServerCommand.java:43)
at io.dropwizard.cli.EnvironmentCommand.run(EnvironmentCommand.java:43)
at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:76)
at io.dropwizard.cli.Cli.run(Cli.java:70)
at io.dropwizard.Application.run(Application.java:72)
at 
com.apache.eagle.service.app.TestServiceAppWithZk.setUp(TestServiceAppWithZk.java:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:120)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:103)
at org.apache.maven.surefire.Surefire.run(Surefire.java:169)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350)
at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021)
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at 
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at 
org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:264)
at 
org.eclipse.jetty.setuid.SetUIDListener.lifeCycleStarting(SetUIDListener.java:200)
... 36 more
{code}



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

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

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

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

ASF GitHub Bot commented on EAGLE-522:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/426
  
@pkuwm there are conflicts, could you please help fix it?


> 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-21 Thread haoch 
Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/426
  
@pkuwm there are conflicts, could you please help fix it?


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