date:20161020

[GitHub] incubator-eagle pull request #379: EAGLE-348 Alert engine base on spark stre...

2016-10-20 Thread r7raul1984

Github user r7raul1984 closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Assigned] (EAGLE-652) services health check for hdfs,hbase and yarn

2016-10-20 Thread yupu (JIRA)


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

yupu reassigned EAGLE-652:
--

Assignee: yupu

> services health check for hdfs,hbase and yarn
> -
>
> Key: EAGLE-652
> URL: https://issues.apache.org/jira/browse/EAGLE-652
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
>
> The app aims to monitor those services with a master-slave structured 
> topology, and provides metrics at the HOST level. Specifically, this app will 
> support the following services healthy check
> •HDFS: namenode, datanode, journalnode
> •HBASE: hmaster, regionservers
> YARN: resourcemanager, nodemanagers, historyserver



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

[GitHub] incubator-eagle issue #546: EAGLE-652:add topology health check to app frame...

2016-10-20 Thread puyulu

Github user puyulu commented on the issue:

https://github.com/apache/incubator-eagle/pull/546
  
removed the unused code after code review


---
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 #546: EAGLE-652:add topology health check to ap...

2016-10-20 Thread puyulu

Github user puyulu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/546#discussion_r84413424
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/extractor/hdfs/HdfsTopologyEntityParser.java
 ---
@@ -220,7 +220,7 @@ private void createAllDataNodeEntities(JMXBean bean, 
long updateTime, TopologyEn
 final String hostname = liveNodes.getString(i);
 final JSONObject liveNode = 
jsonNodesObject.getJSONObject(hostname);
 
-HdfsServiceTopologyAPIEntity entity = 
createHdfsServiceEntity(TopologyConstants.DATA_NODE_ROLE, hostname, updateTime);
+HdfsServiceTopologyAPIEntity entity = 
createHdfsServiceEntity(TopologyConstants.DATA_NODE_ROLE, 
EntityBuilderHelper.getValidHostName(hostname), updateTime);
 final Number configuredCapacity = (Number) 
liveNode.get(DATA_NODE_CAPACITY);
 
entity.setConfiguredCapacityTB(Double.toString(configuredCapacity.doubleValue() 
/ 1024.0 / 1024.0 / 1024.0 / 1024.0));
--- End diff --

changed the hard code to final value


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-652) services health check for hdfs,hbase and yarn

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-652:
--

Github user puyulu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/546#discussion_r84413424
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/extractor/hdfs/HdfsTopologyEntityParser.java
 ---
@@ -220,7 +220,7 @@ private void createAllDataNodeEntities(JMXBean bean, 
long updateTime, TopologyEn
 final String hostname = liveNodes.getString(i);
 final JSONObject liveNode = 
jsonNodesObject.getJSONObject(hostname);
 
-HdfsServiceTopologyAPIEntity entity = 
createHdfsServiceEntity(TopologyConstants.DATA_NODE_ROLE, hostname, updateTime);
+HdfsServiceTopologyAPIEntity entity = 
createHdfsServiceEntity(TopologyConstants.DATA_NODE_ROLE, 
EntityBuilderHelper.getValidHostName(hostname), updateTime);
 final Number configuredCapacity = (Number) 
liveNode.get(DATA_NODE_CAPACITY);
 
entity.setConfiguredCapacityTB(Double.toString(configuredCapacity.doubleValue() 
/ 1024.0 / 1024.0 / 1024.0 / 1024.0));
--- End diff --

changed the hard code to final value


> services health check for hdfs,hbase and yarn
> -
>
> Key: EAGLE-652
> URL: https://issues.apache.org/jira/browse/EAGLE-652
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>  Labels: features
>
> The app aims to monitor those services with a master-slave structured 
> topology, and provides metrics at the HOST level. Specifically, this app will 
> support the following services healthy check
> •HDFS: namenode, datanode, journalnode
> •HBASE: hmaster, regionservers
> YARN: resourcemanager, nodemanagers, historyserver



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

[GitHub] incubator-eagle pull request #546: EAGLE-652:add topology health check to ap...

2016-10-20 Thread puyulu

Github user puyulu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/546#discussion_r84413365
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/resources/META-INF/providers/org.apache.eagle.topology.TopologyCheckAppProvider.xml
 ---
@@ -22,7 +22,6 @@
 Topology Health Check
 0.5.0-incubating
 org.apache.eagle.topology.TopologyCheckApp
--- End diff --

removed unuse class name


---
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-652) services health check for hdfs,hbase and yarn

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-652:
--

Github user puyulu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/546#discussion_r84413365
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/resources/META-INF/providers/org.apache.eagle.topology.TopologyCheckAppProvider.xml
 ---
@@ -22,7 +22,6 @@
 Topology Health Check
 0.5.0-incubating
 org.apache.eagle.topology.TopologyCheckApp
--- End diff --

removed unuse class name


> services health check for hdfs,hbase and yarn
> -
>
> Key: EAGLE-652
> URL: https://issues.apache.org/jira/browse/EAGLE-652
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>  Labels: features
>
> The app aims to monitor those services with a master-slave structured 
> topology, and provides metrics at the HOST level. Specifically, this app will 
> support the following services healthy check
> •HDFS: namenode, datanode, journalnode
> •HBASE: hmaster, regionservers
> YARN: resourcemanager, nodemanagers, historyserver



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

[jira] [Commented] (EAGLE-652) services health check for hdfs,hbase and yarn

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-652:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/540
  
What's the relationship of this ticket with #546 ?


> services health check for hdfs,hbase and yarn
> -
>
> Key: EAGLE-652
> URL: https://issues.apache.org/jira/browse/EAGLE-652
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>  Labels: features
>
> The app aims to monitor those services with a master-slave structured 
> topology, and provides metrics at the HOST level. Specifically, this app will 
> support the following services healthy check
> •HDFS: namenode, datanode, journalnode
> •HBASE: hmaster, regionservers
> YARN: resourcemanager, nodemanagers, historyserver



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

[GitHub] incubator-eagle issue #540: EAGLE-652 : get valid hostname for datanode

2016-10-20 Thread haoch

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/540
  
What's the relationship of this ticket with #546 ?


---
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 #546: EAGLE-652:add topology health check to ap...

2016-10-20 Thread haoch

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/546#discussion_r84412334
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/resources/META-INF/providers/org.apache.eagle.topology.TopologyCheckAppProvider.xml
 ---
@@ -22,7 +22,6 @@
 Topology Health Check
 0.5.0-incubating
 org.apache.eagle.topology.TopologyCheckApp
--- End diff --

`appClass` is useless as well


---
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-652) services health check for hdfs,hbase and yarn

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-652:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/546
  
LGTM if you could fix above two small issues.


> services health check for hdfs,hbase and yarn
> -
>
> Key: EAGLE-652
> URL: https://issues.apache.org/jira/browse/EAGLE-652
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>  Labels: features
>
> The app aims to monitor those services with a master-slave structured 
> topology, and provides metrics at the HOST level. Specifically, this app will 
> support the following services healthy check
> •HDFS: namenode, datanode, journalnode
> •HBASE: hmaster, regionservers
> YARN: resourcemanager, nodemanagers, historyserver



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

[GitHub] incubator-eagle issue #546: EAGLE-652:add topology health check to app frame...

2016-10-20 Thread haoch

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/546
  
LGTM if you could fix above two small issues.


---
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-652) services health check for hdfs,hbase and yarn

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-652:
--

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/546#discussion_r84412447
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/extractor/hdfs/HdfsTopologyEntityParser.java
 ---
@@ -220,7 +220,7 @@ private void createAllDataNodeEntities(JMXBean bean, 
long updateTime, TopologyEn
 final String hostname = liveNodes.getString(i);
 final JSONObject liveNode = 
jsonNodesObject.getJSONObject(hostname);
 
-HdfsServiceTopologyAPIEntity entity = 
createHdfsServiceEntity(TopologyConstants.DATA_NODE_ROLE, hostname, updateTime);
+HdfsServiceTopologyAPIEntity entity = 
createHdfsServiceEntity(TopologyConstants.DATA_NODE_ROLE, 
EntityBuilderHelper.getValidHostName(hostname), updateTime);
 final Number configuredCapacity = (Number) 
liveNode.get(DATA_NODE_CAPACITY);
 
entity.setConfiguredCapacityTB(Double.toString(configuredCapacity.doubleValue() 
/ 1024.0 / 1024.0 / 1024.0 / 1024.0));
--- End diff --

Use static final value `Long TB = 1024.0*1024.0*1024.0*1024.0` then use 

~~~

entity.setConfiguredCapacityTB(Double.toString(configuredCapacity.doubleValue() 
/ TB));
~~~


> services health check for hdfs,hbase and yarn
> -
>
> Key: EAGLE-652
> URL: https://issues.apache.org/jira/browse/EAGLE-652
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>  Labels: features
>
> The app aims to monitor those services with a master-slave structured 
> topology, and provides metrics at the HOST level. Specifically, this app will 
> support the following services healthy check
> •HDFS: namenode, datanode, journalnode
> •HBASE: hmaster, regionservers
> YARN: resourcemanager, nodemanagers, historyserver



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

[GitHub] incubator-eagle pull request #546: EAGLE-652:add topology health check to ap...

2016-10-20 Thread haoch

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/546#discussion_r84412447
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/extractor/hdfs/HdfsTopologyEntityParser.java
 ---
@@ -220,7 +220,7 @@ private void createAllDataNodeEntities(JMXBean bean, 
long updateTime, TopologyEn
 final String hostname = liveNodes.getString(i);
 final JSONObject liveNode = 
jsonNodesObject.getJSONObject(hostname);
 
-HdfsServiceTopologyAPIEntity entity = 
createHdfsServiceEntity(TopologyConstants.DATA_NODE_ROLE, hostname, updateTime);
+HdfsServiceTopologyAPIEntity entity = 
createHdfsServiceEntity(TopologyConstants.DATA_NODE_ROLE, 
EntityBuilderHelper.getValidHostName(hostname), updateTime);
 final Number configuredCapacity = (Number) 
liveNode.get(DATA_NODE_CAPACITY);
 
entity.setConfiguredCapacityTB(Double.toString(configuredCapacity.doubleValue() 
/ 1024.0 / 1024.0 / 1024.0 / 1024.0));
--- End diff --

Use static final value `Long TB = 1024.0*1024.0*1024.0*1024.0` then use 

~~~

entity.setConfiguredCapacityTB(Double.toString(configuredCapacity.doubleValue() 
/ TB));
~~~


---
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-652) services health check for hdfs,hbase and yarn

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-652:
--

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/546#discussion_r84412334
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/resources/META-INF/providers/org.apache.eagle.topology.TopologyCheckAppProvider.xml
 ---
@@ -22,7 +22,6 @@
 Topology Health Check
 0.5.0-incubating
 org.apache.eagle.topology.TopologyCheckApp
--- End diff --

`appClass` is useless as well


> services health check for hdfs,hbase and yarn
> -
>
> Key: EAGLE-652
> URL: https://issues.apache.org/jira/browse/EAGLE-652
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>  Labels: features
>
> The app aims to monitor those services with a master-slave structured 
> topology, and provides metrics at the HOST level. Specifically, this app will 
> support the following services healthy check
> •HDFS: namenode, datanode, journalnode
> •HBASE: hmaster, regionservers
> YARN: resourcemanager, nodemanagers, historyserver



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

[jira] [Commented] (EAGLE-652) services health check for hdfs,hbase and yarn

2016-10-20 Thread Hao Chen (JIRA)


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

Hao Chen commented on EAGLE-652:


@yulu Could you please assign the ticket to yourself?

> services health check for hdfs,hbase and yarn
> -
>
> Key: EAGLE-652
> URL: https://issues.apache.org/jira/browse/EAGLE-652
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>  Labels: features
>
> The app aims to monitor those services with a master-slave structured 
> topology, and provides metrics at the HOST level. Specifically, this app will 
> support the following services healthy check
> •HDFS: namenode, datanode, journalnode
> •HBASE: hmaster, regionservers
> YARN: resourcemanager, nodemanagers, historyserver



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

[jira] [Closed] (EAGLE-655) Fix metadata bug

2016-10-20 Thread wujinhu (JIRA)


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

wujinhu closed EAGLE-655.
-
Resolution: Fixed

> Fix metadata bug
> 
>
> Key: EAGLE-655
> URL: https://issues.apache.org/jira/browse/EAGLE-655
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> fix metadata bug, context saved to metastore



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

[jira] [Commented] (EAGLE-656) Integrate metric system with application framework

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-656:
--

Github user asfgit closed the pull request at:

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


> Integrate metric system with application framework
> --
>
> Key: EAGLE-656
> URL: https://issues.apache.org/jira/browse/EAGLE-656
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Integrate metric system with application framework



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

[GitHub] incubator-eagle pull request #544: [EAGLE-656] Integrate metric system with ...

2016-10-20 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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-652) services health check for hdfs,hbase and yarn

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-652:
--

GitHub user puyulu opened a pull request:

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

EAGLE-652:add topology health check to app framework

add topology health check to app framework

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

$ git pull https://github.com/puyulu/incubator-eagle master

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

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


commit 98a1f41ca7b60fea081ee773b98df67edb7e815d
Author: yupu 
Date:   2016-10-20T11:47:03Z

add health check to pom

commit fdef2256d59fec37bfa071f3724ec95d4a9a8518
Author: yupu 
Date:   2016-10-20T11:54:33Z

get valid hostname for hadoop 2.7




> services health check for hdfs,hbase and yarn
> -
>
> Key: EAGLE-652
> URL: https://issues.apache.org/jira/browse/EAGLE-652
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>  Labels: features
>
> The app aims to monitor those services with a master-slave structured 
> topology, and provides metrics at the HOST level. Specifically, this app will 
> support the following services healthy check
> •HDFS: namenode, datanode, journalnode
> •HBASE: hmaster, regionservers
> YARN: resourcemanager, nodemanagers, historyserver



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

[GitHub] incubator-eagle pull request #546: EAGLE-652:add topology health check to ap...

2016-10-20 Thread puyulu

GitHub user puyulu opened a pull request:

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

EAGLE-652:add topology health check to app framework

add topology health check to app framework

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

$ git pull https://github.com/puyulu/incubator-eagle master

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

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


commit 98a1f41ca7b60fea081ee773b98df67edb7e815d
Author: yupu 
Date:   2016-10-20T11:47:03Z

add health check to pom

commit fdef2256d59fec37bfa071f3724ec95d4a9a8518
Author: yupu 
Date:   2016-10-20T11:54:33Z

get valid hostname for hadoop 2.7




---
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-652) services health check for hdfs,hbase and yarn

2016-10-20 Thread yupu (JIRA)


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

yupu updated EAGLE-652:
---
Affects Version/s: v0.5.0

> services health check for hdfs,hbase and yarn
> -
>
> Key: EAGLE-652
> URL: https://issues.apache.org/jira/browse/EAGLE-652
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>  Labels: features
>
> The app aims to monitor those services with a master-slave structured 
> topology, and provides metrics at the HOST level. Specifically, this app will 
> support the following services healthy check
> •HDFS: namenode, datanode, journalnode
> •HBASE: hmaster, regionservers
> YARN: resourcemanager, nodemanagers, historyserver



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

[jira] [Updated] (EAGLE-652) services health check for hdfs,hbase and yarn

2016-10-20 Thread yupu (JIRA)


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

yupu updated EAGLE-652:
---
Labels: features  (was: )

> services health check for hdfs,hbase and yarn
> -
>
> Key: EAGLE-652
> URL: https://issues.apache.org/jira/browse/EAGLE-652
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>  Labels: features
>
> The app aims to monitor those services with a master-slave structured 
> topology, and provides metrics at the HOST level. Specifically, this app will 
> support the following services healthy check
> •HDFS: namenode, datanode, journalnode
> •HBASE: hmaster, regionservers
> YARN: resourcemanager, nodemanagers, historyserver



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

[jira] [Updated] (EAGLE-652) services health check for hdfs,hbase and yarn

2016-10-20 Thread yupu (JIRA)


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

yupu updated EAGLE-652:
---
Summary: services health check for hdfs,hbase and yarn  (was: topology 
health check)

> services health check for hdfs,hbase and yarn
> -
>
> Key: EAGLE-652
> URL: https://issues.apache.org/jira/browse/EAGLE-652
> Project: Eagle
>  Issue Type: New Feature
>Reporter: yupu
>
> The app aims to monitor those services with a master-slave structured 
> topology, and provides metrics at the HOST level. Specifically, this app will 
> support the following services healthy check
> •HDFS: namenode, datanode, journalnode
> •HBASE: hmaster, regionservers
> YARN: resourcemanager, nodemanagers, historyserver



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

[jira] [Updated] (EAGLE-652) topology health check

2016-10-20 Thread yupu (JIRA)


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

yupu updated EAGLE-652:
---
Description: 

The app aims to monitor those services with a master-slave structured topology, 
and provides metrics at the HOST level. Specifically, this app will support the 
following services healthy check

•HDFS: namenode, datanode, journalnode


•HBASE: hmaster, regionservers

YARN: resourcemanager, nodemanagers, historyserver


  was:topology health check for eagle


> topology health check
> -
>
> Key: EAGLE-652
> URL: https://issues.apache.org/jira/browse/EAGLE-652
> Project: Eagle
>  Issue Type: New Feature
>Reporter: yupu
>
> The app aims to monitor those services with a master-slave structured 
> topology, and provides metrics at the HOST level. Specifically, this app will 
> support the following services healthy check
> •HDFS: namenode, datanode, journalnode
> •HBASE: hmaster, regionservers
> YARN: resourcemanager, nodemanagers, historyserver



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

[jira] [Commented] (EAGLE-647) Support Policy Execution Interpreter and Planner to compile siddhi query to distributed execution plan

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-647:
--

Github user asfgit closed the pull request at:

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


> Support Policy Execution Interpreter and Planner to compile siddhi query to 
> distributed execution plan
> --
>
> Key: EAGLE-647
> URL: https://issues.apache.org/jira/browse/EAGLE-647
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Support Policy Execution Interpreter and Planner to compile siddhi query to 
> distributed execution plan
> * Support parse siddhi pattern and join query as distributed execution
> * Support alias in inner join condition
> * Refactor PolicyIntepreter to eagle-alert-engine and decoupel 
> PolicyExecutionPlanner
> * Fix factory method for PolicyExecutionPlanner



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

[GitHub] incubator-eagle pull request #539: [MINOR] Resolve unstable UT and clean slf...

2016-10-20 Thread haoch

GitHub user haoch opened a pull request:

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

[MINOR] Resolve unstable UT and clean slf4j-log4j dependencies

Resolve unstable UT and clean useless `slf4j-log4j` dependencies.

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

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

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

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


commit ca386752578e2b0dde51c0715511907c4616b311
Author: Hao Chen 
Date:   2016-10-20T08:59:57Z

Resolve unstable UT and clean slf4j-log4j dependencies




---
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 #542: [EAGLE-653] remove zk root from configure

2016-10-20 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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-658) Add reserved "global" siteId as shared namespace

2016-10-20 Thread Hao Chen (JIRA)

Hao Chen created EAGLE-658:
--

 Summary: Add reserved "global" siteId as shared namespace
 Key: EAGLE-658
 URL: https://issues.apache.org/jira/browse/EAGLE-658
 Project: Eagle
  Issue Type: New Feature
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] [Created] (EAGLE-657) EagleServiceMetricSink

2016-10-20 Thread Hao Chen (JIRA)

Hao Chen created EAGLE-657:
--

 Summary: EagleServiceMetricSink
 Key: EAGLE-657
 URL: https://issues.apache.org/jira/browse/EAGLE-657
 Project: Eagle
  Issue Type: New Feature
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.5.0


Persist metric to eagle metric store

{code}
{
metric {
   enabled: true
}
}
{code}



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

[jira] [Updated] (EAGLE-657) EagleServiceMetricSink

2016-10-20 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-657:
---
Description: 
Persist metric to eagle metric store

{code}
{
metric {
   enable: true
}
}
{code}

  was:
Persist metric to eagle metric store

{code}
{
metric {
   enabled: true
}
}
{code}


> EagleServiceMetricSink
> --
>
> Key: EAGLE-657
> URL: https://issues.apache.org/jira/browse/EAGLE-657
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Persist metric to eagle metric store
> {code}
> {
> metric {
>enable: true
> }
> }
> {code}



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

[GitHub] incubator-eagle pull request #537: [EAGLE-642] move application runtime conf...

2016-10-20 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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-653) remove zk root from configure

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-653:
--

Github user asfgit closed the pull request at:

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


> remove zk root from configure
> -
>
> Key: EAGLE-653
> URL: https://issues.apache.org/jira/browse/EAGLE-653
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> add applicationListener to MR feeders so that they can check some 
> environments like connection... before they start



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

[jira] [Commented] (EAGLE-655) Fix metadata bug

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-655:
--

Github user asfgit closed the pull request at:

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


> Fix metadata bug
> 
>
> Key: EAGLE-655
> URL: https://issues.apache.org/jira/browse/EAGLE-655
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> fix metadata bug, context saved to metastore



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

[GitHub] incubator-eagle pull request #545: [EAGLE-655] fix metadata bug

2016-10-20 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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 #543: [MINOR] Fix cobertura.totalLineRate as 25...

2016-10-20 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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 #544: [EAGLE-656] Integrate metric system with ...

2016-10-20 Thread haoch

GitHub user haoch opened a pull request:

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

[EAGLE-656] Integrate metric system with application framework

Integrate metric system with application framework

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

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

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

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

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


commit b20ef751789ccead84cc1cc01919eb87b3e402e3
Author: Hao Chen 
Date:   2016-10-20T12:28:55Z

Integrate metric system with application framework




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

2016-10-20 Thread puyulu

Github user puyulu commented on the pull request:


https://github.com/apache/incubator-eagle/commit/ec0e8af4a25e8021f9f7749f73b56cd6b715a7bd#commitcomment-19499797
  
change topoloy check to topology app


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Closed] (EAGLE-653) remove zk root from configure

2016-10-20 Thread wujinhu (JIRA)


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

wujinhu closed EAGLE-653.
-
Resolution: Resolved

> remove zk root from configure
> -
>
> Key: EAGLE-653
> URL: https://issues.apache.org/jira/browse/EAGLE-653
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> add applicationListener to MR feeders so that they can check some 
> environments like connection... before they start



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

[EAGLE TEST FAILED] incubator-eagle-main failed in testing phase on build #225

2016-10-20 Thread Apache Jenkins Server

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

[GitHub] incubator-eagle pull request #538: EAGLE-646: AlertUnitTopology does not reb...

2016-10-20 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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 #540: EAGLE-652 : get valid hostname for datanode

2016-10-20 Thread haoch

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/540
  
Before move on to merge the PR, could you please clean up the changes? Why 
`+566`  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-642) move application runtime configure to ApplicationEntity context

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-642:
--

Github user asfgit closed the pull request at:

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


> move application runtime configure to ApplicationEntity context
> ---
>
> Key: EAGLE-642
> URL: https://issues.apache.org/jira/browse/EAGLE-642
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> When install an application, there are some configures like appId/siteId that 
> should not changed by user, so we move them to context.



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

[jira] [Commented] (EAGLE-652) topology health check

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-652:
--

GitHub user puyulu opened a pull request:

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

EAGLE-652 : get valid hostname for datanode

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

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

$ git pull https://github.com/puyulu/incubator-eagle master

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

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


commit 66b198f9a1389795aed0a825be05dee7dd03356c
Author: yupu 
Date:   2016-10-20T09:33:21Z

get valid hostname for datanode




> topology health check
> -
>
> Key: EAGLE-652
> URL: https://issues.apache.org/jira/browse/EAGLE-652
> Project: Eagle
>  Issue Type: New Feature
>Reporter: yupu
>
> topology health check for eagle



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

[GitHub] incubator-eagle pull request #540: EAGLE-652 : get valid hostname for datano...

2016-10-20 Thread puyulu

GitHub user puyulu opened a pull request:

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

EAGLE-652 : get valid hostname for datanode

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

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

$ git pull https://github.com/puyulu/incubator-eagle master

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

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


commit 66b198f9a1389795aed0a825be05dee7dd03356c
Author: yupu 
Date:   2016-10-20T09:33:21Z

get valid hostname for datanode




---
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-653) remove zk root from configure

2016-10-20 Thread wujinhu (JIRA)


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

wujinhu updated EAGLE-653:
--
Summary: remove zk root from configure  (was: Add ApplicationListener To MR 
Feeders)

> remove zk root from configure
> -
>
> Key: EAGLE-653
> URL: https://issues.apache.org/jira/browse/EAGLE-653
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> add applicationListener to MR feeders so that they can check some 
> environments like connection... before they start



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

[jira] [Commented] (EAGLE-653) remove zk root from configure

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-653:
--

GitHub user wujinhu opened a pull request:

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

[EAGLE-653] remove zk root from configure



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

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

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

https://github.com/apache/incubator-eagle/pull/542.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #542


commit 19824483bf41dc5e6bd3f7308b25f771ea64805d
Author: wujinhu 
Date:   2016-10-20T10:31:36Z

remove zk root from configure




> remove zk root from configure
> -
>
> Key: EAGLE-653
> URL: https://issues.apache.org/jira/browse/EAGLE-653
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> add applicationListener to MR feeders so that they can check some 
> environments like connection... before they start



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

[jira] [Updated] (EAGLE-651) HBase JMX Metric Monitoring Application

2016-10-20 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-651:
---
Description: 
HBase Master JMX Monitoring
HBase Region  Server Jmx Monitoring

  was:HBase Master JMX Monitoring


> HBase JMX Metric Monitoring Application
> ---
>
> Key: EAGLE-651
> URL: https://issues.apache.org/jira/browse/EAGLE-651
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> HBase Master JMX Monitoring
> HBase Region  Server Jmx Monitoring



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

[GitHub] incubator-eagle pull request #538: EAGLE-646: AlertUnitTopology does not reb...

2016-10-20 Thread haoch

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/538#discussion_r84228412
  
--- Diff: 
eagle-core/eagle-alert-parent/eagle-alert-app/src/main/java/org/apache/eagle/alert/app/AlertUnitTopologyAppListener.java
 ---
@@ -73,6 +74,7 @@ private void updateTopologyMetadata() {
 LOG.error(result.message);
 throw new IllegalStateException(result.message);
 }
+Coordinator.startSchedule();
--- End diff --

Please call `build` 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.
---

[jira] [Commented] (EAGLE-642) move application runtime configure to ApplicationEntity context

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-642:
--

GitHub user wujinhu opened a pull request:

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

[EAGLE-642] move application runtime configure to ApplicationEntity context



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

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

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

https://github.com/apache/incubator-eagle/pull/537.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #537


commit 7e6dc2edbfb678cc39be51290d4585e4e43f2a37
Author: wujinhu 
Date:   2016-10-20T06:36:07Z

move application runtime configure to ApplicationEntity context




> move application runtime configure to ApplicationEntity context
> ---
>
> Key: EAGLE-642
> URL: https://issues.apache.org/jira/browse/EAGLE-642
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> When install an application, there are some configures like appId/siteId that 
> should not changed by user, so we move them to context.



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

[EAGLE TEST FAILED] incubator-eagle-main failed in testing phase on build #226

2016-10-20 Thread Apache Jenkins Server

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

[jira] [Updated] (EAGLE-651) HBase JMX Metric Monitoring Application

2016-10-20 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-651:
---
Description: HBase Master JMX Monitoring  (was: HBase Master JMX Monitoring
HBase Region  Server Jmx Monitoring)

> HBase JMX Metric Monitoring Application
> ---
>
> Key: EAGLE-651
> URL: https://issues.apache.org/jira/browse/EAGLE-651
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> HBase Master JMX Monitoring



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

[jira] [Created] (EAGLE-651) HBase JMX Metric Monitoring Application

2016-10-20 Thread Hao Chen (JIRA)

Hao Chen created EAGLE-651:
--

 Summary: HBase JMX Metric Monitoring Application
 Key: EAGLE-651
 URL: https://issues.apache.org/jira/browse/EAGLE-651
 Project: Eagle
  Issue Type: New Feature
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.5.0


HBase Master JMX Monitoring



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

[GitHub] incubator-eagle pull request #542: [EAGLE-653] remove zk root from configure

2016-10-20 Thread wujinhu

GitHub user wujinhu opened a pull request:

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

[EAGLE-653] remove zk root from configure



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

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

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

https://github.com/apache/incubator-eagle/pull/542.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #542


commit 19824483bf41dc5e6bd3f7308b25f771ea64805d
Author: wujinhu 
Date:   2016-10-20T10:31:36Z

remove zk root from configure




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request #539: [MINOR] Resolve unstable UT and clean slf...

2016-10-20 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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 #541: EAGLE-648: Stream router does not work pr...

2016-10-20 Thread garrettlish

GitHub user garrettlish opened a pull request:

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

EAGLE-648: Stream router does not work properly sometimes

Stream router does not work properly when multiple policies use the same 
input stream with the same partition definition. It is because stream router 
bolt output maintains a map of the route specs, but the key of the map is 
streamId + partition information. The monitor stream may override each other if 
the streamId and partition are the same.

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


commit 21488410c091cd356a5e13f7b53c3ba2e51bcae1
Author: Xiancheng Li 
Date:   2016-10-20T10:06:38Z

EAGLE-648: Stream router does not work properly sometimes




---
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 TEST FAILED] incubator-eagle-main failed in testing phase on build #227

2016-10-20 Thread Apache Jenkins Server

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

[jira] [Created] (EAGLE-653) Add ApplicationListener To MR Feeders

2016-10-20 Thread wujinhu (JIRA)

wujinhu created EAGLE-653:
-

 Summary: Add ApplicationListener To MR Feeders
 Key: EAGLE-653
 URL: https://issues.apache.org/jira/browse/EAGLE-653
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: wujinhu
 Fix For: v0.5.0


add applicationListener to MR feeders so that they can check some environments 
like connection... before they start



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

[GitHub] incubator-eagle pull request #537: [EAGLE-642] move application runtime conf...

2016-10-20 Thread wujinhu

GitHub user wujinhu opened a pull request:

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

[EAGLE-642] move application runtime configure to ApplicationEntity context



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

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

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

https://github.com/apache/incubator-eagle/pull/537.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #537


commit 7e6dc2edbfb678cc39be51290d4585e4e43f2a37
Author: wujinhu 
Date:   2016-10-20T06:36:07Z

move application runtime configure to ApplicationEntity context




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request #536: [EAGLE-647] Support Policy Execution Inte...

2016-10-20 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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 #538: EAGLE-646: AlertUnitTopology does not reb...

2016-10-20 Thread qingwen220

GitHub user qingwen220 opened a pull request:

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

EAGLE-646: AlertUnitTopology does not rebuild the scheduler state after 
restarting  

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

1. Fix a bug that alertUnitTopology does not rebuild the scheduler state 
after restarting
2. Fix topology assembly dependency bug 


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

$ git pull https://github.com/qingwen220/incubator-eagle EAGLE-646

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

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


commit 723699d3111f55d4bb674ced35f25aac86ab0662
Author: Zhao, Qingwen 
Date:   2016-10-20T05:31:58Z

Add coordinator build in AlertUnitTopology listener

commit 84b92063f8ccd94288d355b18f469e8318f7aaf4
Author: Zhao, Qingwen 
Date:   2016-10-20T07:04:00Z

Fix topology-assembly dependency




---
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-646) AlertUnitTopology does not rebuild the scheduler state after restarting

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-646:
--

Github user haoch commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/538#discussion_r84228412
  
--- Diff: 
eagle-core/eagle-alert-parent/eagle-alert-app/src/main/java/org/apache/eagle/alert/app/AlertUnitTopologyAppListener.java
 ---
@@ -73,6 +74,7 @@ private void updateTopologyMetadata() {
 LOG.error(result.message);
 throw new IllegalStateException(result.message);
 }
+Coordinator.startSchedule();
--- End diff --

Please call `build` directly.


> AlertUnitTopology does not rebuild the scheduler state after restarting
> ---
>
> Key: EAGLE-646
> URL: https://issues.apache.org/jira/browse/EAGLE-646
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> AlertUnitTopology does not rebuild the scheduler state after restarting, 
> which leads to messages fail frequently if users change the topology 
> configuration



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

[jira] [Commented] (EAGLE-646) AlertUnitTopology does not rebuild the scheduler state after restarting

2016-10-20 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on EAGLE-646:
--

GitHub user qingwen220 opened a pull request:

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

EAGLE-646: AlertUnitTopology does not rebuild the scheduler state after 
restarting  

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

1. Fix a bug that alertUnitTopology does not rebuild the scheduler state 
after restarting
2. Fix topology assembly dependency bug 


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

$ git pull https://github.com/qingwen220/incubator-eagle EAGLE-646

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

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


commit 723699d3111f55d4bb674ced35f25aac86ab0662
Author: Zhao, Qingwen 
Date:   2016-10-20T05:31:58Z

Add coordinator build in AlertUnitTopology listener

commit 84b92063f8ccd94288d355b18f469e8318f7aaf4
Author: Zhao, Qingwen 
Date:   2016-10-20T07:04:00Z

Fix topology-assembly dependency




> AlertUnitTopology does not rebuild the scheduler state after restarting
> ---
>
> Key: EAGLE-646
> URL: https://issues.apache.org/jira/browse/EAGLE-646
> Project: Eagle
>  Issue Type: Bug
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>
> AlertUnitTopology does not rebuild the scheduler state after restarting, 
> which leads to messages fail frequently if users change the topology 
> configuration



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

[jira] [Updated] (EAGLE-650) Hadoop JMX Metric Monitoring Application

2016-10-20 Thread Hao Chen (JIRA)


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

Hao Chen updated EAGLE-650:
---
Summary: Hadoop JMX Metric Monitoring Application  (was: Hadoop JMX 
Monitoring Application)

> Hadoop JMX Metric Monitoring Application
> 
>
> Key: EAGLE-650
> URL: https://issues.apache.org/jira/browse/EAGLE-650
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Hadoop JMX Monitoring Application
> * Hadoop Namenode JMX
> * Hadoop Resource Manager JMX



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

[jira] [Created] (EAGLE-650) Hadoop JMX Monitoring Application

2016-10-20 Thread Hao Chen (JIRA)

Hao Chen created EAGLE-650:
--

 Summary: Hadoop JMX Monitoring Application
 Key: EAGLE-650
 URL: https://issues.apache.org/jira/browse/EAGLE-650
 Project: Eagle
  Issue Type: New Feature
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.5.0


Hadoop JMX Monitoring Application
* Hadoop Namenode JMX
* Hadoop Resource Manager JMX



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

65 matches

Mail list logo