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

[Apache Jenkins Server]

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

[GitHub] incubator-eagle pull request #570: EAGLE-690 : integrage topology health che...

[haoch]

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r86078122
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/TopologyCheckApp.java
 ---
@@ -45,7 +63,16 @@ public StormTopology execute(Config config, 
StormEnvironment environment) {
 persistBoltName,
 new TopologyDataPersistBolt(topologyCheckAppConfig),
 topologyCheckAppConfig.dataExtractorConfig.numEntityPersistBolt
-
).setNumTasks(topologyCheckAppConfig.dataExtractorConfig.numEntityPersistBolt).shuffleGrouping(spoutName);
+
).setNumTasks(topologyCheckAppConfig.dataExtractorConfig.numEntityPersistBolt).shuffleGrouping(spoutName);

+   
+topologyBuilder.setBolt(
+   parseBoltName,
+   new HealthCheckParseBolt(),
+   
topologyCheckAppConfig.dataExtractorConfig.numEntityPersistBolt).shuffleGrouping(persistBoltName);
  
+
+logger.info("start to sink messsage to kafka");
--- End diff --

Storm topology is lazy execution, so in fact, current it's just defining 
the execution dataflow but not handle data at all, so `start to sink messsage 
to kafka` is not correct.


---
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-690) Integrate topology health check with alert engine

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-690:
--

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r86078122
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/TopologyCheckApp.java
 ---
@@ -45,7 +63,16 @@ public StormTopology execute(Config config, 
StormEnvironment environment) {
 persistBoltName,
 new TopologyDataPersistBolt(topologyCheckAppConfig),
 topologyCheckAppConfig.dataExtractorConfig.numEntityPersistBolt
-
).setNumTasks(topologyCheckAppConfig.dataExtractorConfig.numEntityPersistBolt).shuffleGrouping(spoutName);
+
).setNumTasks(topologyCheckAppConfig.dataExtractorConfig.numEntityPersistBolt).shuffleGrouping(spoutName);

+   
+topologyBuilder.setBolt(
+   parseBoltName,
+   new HealthCheckParseBolt(),
+   
topologyCheckAppConfig.dataExtractorConfig.numEntityPersistBolt).shuffleGrouping(persistBoltName);
  
+
+logger.info("start to sink messsage to kafka");
--- End diff --

Storm topology is lazy execution, so in fact, current it's just defining 
the execution dataflow but not handle data at all, so `start to sink messsage 
to kafka` is not correct.


> Integrate topology health check with alert engine
> -
>
> Key: EAGLE-690
> URL: https://issues.apache.org/jira/browse/EAGLE-690
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
> Fix For: v0.5.0
>
>
> Integrate topology health check with alert engine.
> It will send timestamp,tag,status to alert engine,when the node status is 
> dead, alert engine will send the email to user



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

[jira] [Commented] (EAGLE-690) Integrate topology health check with alert engine

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-690:
--

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r86078128
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/resources/META-INF/providers/org.apache.eagle.topology.TopologyCheckAppProvider.xml
 ---
@@ -89,28 +97,36 @@
 Hbase Master Principal
 hadoop/_h...@example.com
 
-
+
+
+dataSourceConfig.hbase.kerberos.eagle.principal
+hbaseEaglePrincipal
+Hbase eagle Principal
+
+
--- End diff --

Other config like eagle service should read config through execute(Config 
config, StormEnvironment environment) call.


> Integrate topology health check with alert engine
> -
>
> Key: EAGLE-690
> URL: https://issues.apache.org/jira/browse/EAGLE-690
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
> Fix For: v0.5.0
>
>
> Integrate topology health check with alert engine.
> It will send timestamp,tag,status to alert engine,when the node status is 
> dead, alert engine will send the email to user



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

[GitHub] incubator-eagle pull request #570: EAGLE-690 : integrage topology health che...

[wujinhu]

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r86078128
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/resources/META-INF/providers/org.apache.eagle.topology.TopologyCheckAppProvider.xml
 ---
@@ -89,28 +97,36 @@
 Hbase Master Principal
 hadoop/_h...@example.com
 
-
+
+
+dataSourceConfig.hbase.kerberos.eagle.principal
+hbaseEaglePrincipal
+Hbase eagle Principal
+
+
--- End diff --

Other config like eagle service should read config through execute(Config 
config, StormEnvironment environment) call.


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

[jira] [Commented] (EAGLE-690) Integrate topology health check with alert engine

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-690:
--

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r86078024
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/TopologyCheckApp.java
 ---
@@ -20,20 +20,38 @@
 
 import backtype.storm.generated.StormTopology;
 import backtype.storm.topology.TopologyBuilder;
+
+import com.microsoft.azure.storage.core.Logger;
 import com.typesafe.config.Config;
+
+import org.apache.commons.logging.Log;
+import org.apache.commons.logging.LogFactory;
 import org.apache.eagle.app.StormApplication;
 import org.apache.eagle.app.environment.impl.StormEnvironment;
+import org.apache.eagle.app.sink.StormStreamSink;
+import org.apache.eagle.topology.storm.HealthCheckParseBolt;
 import org.apache.eagle.topology.storm.TopologyCheckAppSpout;
 import org.apache.eagle.topology.storm.TopologyDataPersistBolt;
 
 public class TopologyCheckApp extends StormApplication {
+   /**
--- End diff --

Remove useless comments


> Integrate topology health check with alert engine
> -
>
> Key: EAGLE-690
> URL: https://issues.apache.org/jira/browse/EAGLE-690
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
> Fix For: v0.5.0
>
>
> Integrate topology health check with alert engine.
> It will send timestamp,tag,status to alert engine,when the node status is 
> dead, alert engine will send the email to user



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

[GitHub] incubator-eagle pull request #570: EAGLE-690 : integrage topology health che...

[haoch]

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r86078024
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/TopologyCheckApp.java
 ---
@@ -20,20 +20,38 @@
 
 import backtype.storm.generated.StormTopology;
 import backtype.storm.topology.TopologyBuilder;
+
+import com.microsoft.azure.storage.core.Logger;
 import com.typesafe.config.Config;
+
+import org.apache.commons.logging.Log;
+import org.apache.commons.logging.LogFactory;
 import org.apache.eagle.app.StormApplication;
 import org.apache.eagle.app.environment.impl.StormEnvironment;
+import org.apache.eagle.app.sink.StormStreamSink;
+import org.apache.eagle.topology.storm.HealthCheckParseBolt;
 import org.apache.eagle.topology.storm.TopologyCheckAppSpout;
 import org.apache.eagle.topology.storm.TopologyDataPersistBolt;
 
 public class TopologyCheckApp extends StormApplication {
+   /**
--- End diff --

Remove useless comments


---
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-690) Integrate topology health check with alert engine

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-690:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/570
  
@puyulu what's the progress?


> Integrate topology health check with alert engine
> -
>
> Key: EAGLE-690
> URL: https://issues.apache.org/jira/browse/EAGLE-690
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
> Fix For: v0.5.0
>
>
> Integrate topology health check with alert engine.
> It will send timestamp,tag,status to alert engine,when the node status is 
> dead, alert engine will send the email to user



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

[GitHub] incubator-eagle issue #570: EAGLE-690 : integrage topology health check with...

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/570
  
@puyulu what's the progress?


---
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-690) Integrate topology health check with alert engine

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-690:
--

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r86077566
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/storm/HealthCheckParseBolt.java
 ---
@@ -0,0 +1,84 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+package org.apache.eagle.topology.storm;
+
+import backtype.storm.task.OutputCollector;
+import backtype.storm.task.TopologyContext;
+import backtype.storm.topology.OutputFieldsDeclarer;
+import backtype.storm.topology.base.BaseRichBolt;
+import backtype.storm.tuple.Fields;
+import backtype.storm.tuple.Tuple;
+
+import com.fasterxml.jackson.databind.ObjectMapper;
+
+import org.apache.eagle.topology.TopologyConstants;
+import org.apache.eagle.topology.entity.HealthCheckParseAPIEntity;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import storm.kafka.bolt.mapper.FieldNameBasedTupleToKafkaMapper;
+
+import java.util.Arrays;
+import java.util.Map;
+import java.util.TreeMap;
+
+/**
+ * Since 10/26/16.
+ */
+public class HealthCheckParseBolt extends BaseRichBolt {
+/**
+* 
+*/
+   private static final long serialVersionUID = 1L;
--- End diff --

Please follow code style


> Integrate topology health check with alert engine
> -
>
> Key: EAGLE-690
> URL: https://issues.apache.org/jira/browse/EAGLE-690
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
> Fix For: v0.5.0
>
>
> Integrate topology health check with alert engine.
> It will send timestamp,tag,status to alert engine,when the node status is 
> dead, alert engine will send the email to user



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

[GitHub] incubator-eagle pull request #570: EAGLE-690 : integrage topology health che...

[wujinhu]

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r86077566
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/storm/HealthCheckParseBolt.java
 ---
@@ -0,0 +1,84 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+package org.apache.eagle.topology.storm;
+
+import backtype.storm.task.OutputCollector;
+import backtype.storm.task.TopologyContext;
+import backtype.storm.topology.OutputFieldsDeclarer;
+import backtype.storm.topology.base.BaseRichBolt;
+import backtype.storm.tuple.Fields;
+import backtype.storm.tuple.Tuple;
+
+import com.fasterxml.jackson.databind.ObjectMapper;
+
+import org.apache.eagle.topology.TopologyConstants;
+import org.apache.eagle.topology.entity.HealthCheckParseAPIEntity;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import storm.kafka.bolt.mapper.FieldNameBasedTupleToKafkaMapper;
+
+import java.util.Arrays;
+import java.util.Map;
+import java.util.TreeMap;
+
+/**
+ * Since 10/26/16.
+ */
+public class HealthCheckParseBolt extends BaseRichBolt {
+/**
+* 
+*/
+   private static final long serialVersionUID = 1L;
--- End diff --

Please follow code style


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

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

[Apache Jenkins Server]

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

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-652:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/540
  
@puyulu please close this PR


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

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/540
  
@puyulu please close this PR


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

[jira] [Commented] (EAGLE-680) Can't generate Html coverage report

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-680:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/559
  
LGTM and merged.


> Can't generate Html coverage report 
> 
>
> Key: EAGLE-680
> URL: https://issues.apache.org/jira/browse/EAGLE-680
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Chang chen
>Assignee: Lingang Deng
> Fix For: v0.5.0
>
>
> The Current cobertura plugin just generate xml format by default which is 
> inconvenient  for local verification,



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

[jira] [Commented] (EAGLE-680) Can't generate Html coverage report

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-680:
--

Github user asfgit closed the pull request at:

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


> Can't generate Html coverage report 
> 
>
> Key: EAGLE-680
> URL: https://issues.apache.org/jira/browse/EAGLE-680
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Chang chen
>Assignee: Lingang Deng
> Fix For: v0.5.0
>
>
> The Current cobertura plugin just generate xml format by default which is 
> inconvenient  for local verification,



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

[GitHub] incubator-eagle pull request #559: EAGLE-680 Can't genetate Html coverage re...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #559: EAGLE-680 Can't genetate Html coverage report

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/559
  
LGTM and merged.


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

[jira] [Commented] (EAGLE-717) Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-717:
--

Github user baibaichen commented on the issue:

https://github.com/apache/incubator-eagle/pull/596
  
@haoch  I added  \always\ in the pom.xml, so you 
needn't update PR CI script. It doesn't affect test duration from the  
[testresult](https://builds.apache.org/job/incubator-eagle-pr-reviewer/1139/testReport/)


> Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly
> 
>
> Key: EAGLE-717
> URL: https://issues.apache.org/jira/browse/EAGLE-717
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Chang chen
>Assignee: Chang chen
>  Labels: unit-test
> Fix For: v0.5.0
>
>
> Eagle UT need load siddhi string extension dynamically, but the current 
> maven-surefire-plugin is too old (2.6), and  can't work correctly in always 
> forkMode which is needed for HBase UT. See [Class Loading and Forking in 
> Maven 
> Surefire|http://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html]
>  to understand how maven-surefire-plugin sets *java.class.path* and why.
>  



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

[GitHub] incubator-eagle issue #596: [EAGLE-717] Upgrade maven-surefire-plugin for su...

[baibaichen]

Github user baibaichen commented on the issue:

https://github.com/apache/incubator-eagle/pull/596
  
@haoch  I added  \always\ in the pom.xml, so you 
needn't update PR CI script. It doesn't affect test duration from the  
[testresult](https://builds.apache.org/job/incubator-eagle-pr-reviewer/1139/testReport/)


---
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 #570: EAGLE-690 : integrage topology health check with...

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/570
  
@puyulu please fix according to comments as @qingwen220 and I leave, and 
also modify the `displayName` in configuration section of AppProvider.xml.


---
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-690) Integrate topology health check with alert engine

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-690:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/570
  
@puyulu please fix according to comments as @qingwen220 and I leave, and 
also modify the `displayName` in configuration section of AppProvider.xml.


> Integrate topology health check with alert engine
> -
>
> Key: EAGLE-690
> URL: https://issues.apache.org/jira/browse/EAGLE-690
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
> Fix For: v0.5.0
>
>
> Integrate topology health check with alert engine.
> It will send timestamp,tag,status to alert engine,when the node status is 
> dead, alert engine will send the email to user



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

[jira] [Commented] (EAGLE-690) Integrate topology health check with alert engine

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-690:
--

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r86068136
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/storm/HealthCheckParseBolt.java
 ---
@@ -0,0 +1,84 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+package org.apache.eagle.topology.storm;
+
+import backtype.storm.task.OutputCollector;
+import backtype.storm.task.TopologyContext;
+import backtype.storm.topology.OutputFieldsDeclarer;
+import backtype.storm.topology.base.BaseRichBolt;
+import backtype.storm.tuple.Fields;
+import backtype.storm.tuple.Tuple;
+
+import com.fasterxml.jackson.databind.ObjectMapper;
+
+import org.apache.eagle.topology.TopologyConstants;
+import org.apache.eagle.topology.entity.HealthCheckParseAPIEntity;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import storm.kafka.bolt.mapper.FieldNameBasedTupleToKafkaMapper;
+
+import java.util.Arrays;
+import java.util.Map;
+import java.util.TreeMap;
+
+/**
+ * Since 10/26/16.
+ */
+public class HealthCheckParseBolt extends BaseRichBolt {
+/**
+* 
+*/
+   private static final long serialVersionUID = 1L;
+   
+   private static Logger LOG = 
LoggerFactory.getLogger(HealthCheckParseBolt.class);
+private OutputCollector collector;
+
+@Override
+public void prepare(Map map, TopologyContext topologyContext, 
OutputCollector outputCollector) {
+this.collector = outputCollector;
+}
+
+@Override
+public void execute(Tuple tuple) {
+   HealthCheckParseAPIEntity result = null;
+try{
+   result = (HealthCheckParseAPIEntity) 
tuple.getValueByField("kafkaData");
--- End diff --

Avoid using `kafka` words as it's underly detail.


> Integrate topology health check with alert engine
> -
>
> Key: EAGLE-690
> URL: https://issues.apache.org/jira/browse/EAGLE-690
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
> Fix For: v0.5.0
>
>
> Integrate topology health check with alert engine.
> It will send timestamp,tag,status to alert engine,when the node status is 
> dead, alert engine will send the email to user



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

[GitHub] incubator-eagle pull request #570: EAGLE-690 : integrage topology health che...

[haoch]

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r86068136
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/storm/HealthCheckParseBolt.java
 ---
@@ -0,0 +1,84 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+package org.apache.eagle.topology.storm;
+
+import backtype.storm.task.OutputCollector;
+import backtype.storm.task.TopologyContext;
+import backtype.storm.topology.OutputFieldsDeclarer;
+import backtype.storm.topology.base.BaseRichBolt;
+import backtype.storm.tuple.Fields;
+import backtype.storm.tuple.Tuple;
+
+import com.fasterxml.jackson.databind.ObjectMapper;
+
+import org.apache.eagle.topology.TopologyConstants;
+import org.apache.eagle.topology.entity.HealthCheckParseAPIEntity;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import storm.kafka.bolt.mapper.FieldNameBasedTupleToKafkaMapper;
+
+import java.util.Arrays;
+import java.util.Map;
+import java.util.TreeMap;
+
+/**
+ * Since 10/26/16.
+ */
+public class HealthCheckParseBolt extends BaseRichBolt {
+/**
+* 
+*/
+   private static final long serialVersionUID = 1L;
+   
+   private static Logger LOG = 
LoggerFactory.getLogger(HealthCheckParseBolt.class);
+private OutputCollector collector;
+
+@Override
+public void prepare(Map map, TopologyContext topologyContext, 
OutputCollector outputCollector) {
+this.collector = outputCollector;
+}
+
+@Override
+public void execute(Tuple tuple) {
+   HealthCheckParseAPIEntity result = null;
+try{
+   result = (HealthCheckParseAPIEntity) 
tuple.getValueByField("kafkaData");
--- End diff --

Avoid using `kafka` words as it's underly detail.


---
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-690) Integrate topology health check with alert engine

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-690:
--

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r86068067
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/TopologyCheckAppConfig.java
 ---
@@ -32,6 +32,8 @@
 
 public static final String TOPOLOGY_DATA_FETCH_SPOUT_NAME = 
"topologyDataFetcherSpout";
 public static final String TOPOLOGY_ENTITY_PERSIST_BOLT_NAME = 
"topologyEntityPersistBolt";
+public static final String PARSE_BOLT_NAME = "parserBolt";
+public static final String KAFKA_SINK_BOLT_NAME = "kafkaSinkBolt";
--- End diff --

Please use `sinkBolt` directly instead of `kafkaSinkBolt` as `kafka` is the 
underly implementation of `StreamSink` term.


> Integrate topology health check with alert engine
> -
>
> Key: EAGLE-690
> URL: https://issues.apache.org/jira/browse/EAGLE-690
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
> Fix For: v0.5.0
>
>
> Integrate topology health check with alert engine.
> It will send timestamp,tag,status to alert engine,when the node status is 
> dead, alert engine will send the email to user



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

[GitHub] incubator-eagle pull request #570: EAGLE-690 : integrage topology health che...

[haoch]

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r86068067
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/TopologyCheckAppConfig.java
 ---
@@ -32,6 +32,8 @@
 
 public static final String TOPOLOGY_DATA_FETCH_SPOUT_NAME = 
"topologyDataFetcherSpout";
 public static final String TOPOLOGY_ENTITY_PERSIST_BOLT_NAME = 
"topologyEntityPersistBolt";
+public static final String PARSE_BOLT_NAME = "parserBolt";
+public static final String KAFKA_SINK_BOLT_NAME = "kafkaSinkBolt";
--- End diff --

Please use `sinkBolt` directly instead of `kafkaSinkBolt` as `kafka` is the 
underly implementation of `StreamSink` term.


---
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-690) Integrate topology health check with alert engine

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-690:
--

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r86067973
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/TopologyCheckApp.java
 ---
@@ -20,20 +20,38 @@
 
 import backtype.storm.generated.StormTopology;
 import backtype.storm.topology.TopologyBuilder;
+
+import com.microsoft.azure.storage.core.Logger;
--- End diff --

Please use `slf4j-log` as single standard logging library.


> Integrate topology health check with alert engine
> -
>
> Key: EAGLE-690
> URL: https://issues.apache.org/jira/browse/EAGLE-690
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
> Fix For: v0.5.0
>
>
> Integrate topology health check with alert engine.
> It will send timestamp,tag,status to alert engine,when the node status is 
> dead, alert engine will send the email to user



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

[jira] [Commented] (EAGLE-690) Integrate topology health check with alert engine

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-690:
--

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r86067948
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/TopologyCheckApp.java
 ---
@@ -20,20 +20,38 @@
 
 import backtype.storm.generated.StormTopology;
 import backtype.storm.topology.TopologyBuilder;
+
+import com.microsoft.azure.storage.core.Logger;
 import com.typesafe.config.Config;
+
+import org.apache.commons.logging.Log;
+import org.apache.commons.logging.LogFactory;
 import org.apache.eagle.app.StormApplication;
 import org.apache.eagle.app.environment.impl.StormEnvironment;
+import org.apache.eagle.app.sink.StormStreamSink;
+import org.apache.eagle.topology.storm.HealthCheckParseBolt;
 import org.apache.eagle.topology.storm.TopologyCheckAppSpout;
 import org.apache.eagle.topology.storm.TopologyDataPersistBolt;
 
 public class TopologyCheckApp extends StormApplication {
+   /**
+* 
+*/
+   private static final long serialVersionUID = 1L;
+   
+   private static final String SINK_TASK_NUM = "topology.numOfSinkTasks";
+   private static final String TOPOLOGY_HEALTH_CHECK_STREAM = 
"topology_health_check_stream";
+   Log logger = LogFactory.getLog(TopologyCheckApp.class);
--- End diff --

Use `private static final Logger LOG` for logger things.


> Integrate topology health check with alert engine
> -
>
> Key: EAGLE-690
> URL: https://issues.apache.org/jira/browse/EAGLE-690
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
> Fix For: v0.5.0
>
>
> Integrate topology health check with alert engine.
> It will send timestamp,tag,status to alert engine,when the node status is 
> dead, alert engine will send the email to user



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

[GitHub] incubator-eagle pull request #570: EAGLE-690 : integrage topology health che...

[haoch]

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r86067948
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/TopologyCheckApp.java
 ---
@@ -20,20 +20,38 @@
 
 import backtype.storm.generated.StormTopology;
 import backtype.storm.topology.TopologyBuilder;
+
+import com.microsoft.azure.storage.core.Logger;
 import com.typesafe.config.Config;
+
+import org.apache.commons.logging.Log;
+import org.apache.commons.logging.LogFactory;
 import org.apache.eagle.app.StormApplication;
 import org.apache.eagle.app.environment.impl.StormEnvironment;
+import org.apache.eagle.app.sink.StormStreamSink;
+import org.apache.eagle.topology.storm.HealthCheckParseBolt;
 import org.apache.eagle.topology.storm.TopologyCheckAppSpout;
 import org.apache.eagle.topology.storm.TopologyDataPersistBolt;
 
 public class TopologyCheckApp extends StormApplication {
+   /**
+* 
+*/
+   private static final long serialVersionUID = 1L;
+   
+   private static final String SINK_TASK_NUM = "topology.numOfSinkTasks";
+   private static final String TOPOLOGY_HEALTH_CHECK_STREAM = 
"topology_health_check_stream";
+   Log logger = LogFactory.getLog(TopologyCheckApp.class);
--- End diff --

Use `private static final Logger LOG` for logger things.


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

[GitHub] incubator-eagle pull request #570: EAGLE-690 : integrage topology health che...

[haoch]

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r86067973
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/java/org/apache/eagle/topology/TopologyCheckApp.java
 ---
@@ -20,20 +20,38 @@
 
 import backtype.storm.generated.StormTopology;
 import backtype.storm.topology.TopologyBuilder;
+
+import com.microsoft.azure.storage.core.Logger;
--- End diff --

Please use `slf4j-log` as single standard logging library.


---
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 #596: [EAGLE-717] Upgrade maven-surefire-plugin for su...

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/596
  
@baibaichen what's the command you use for running 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.
---

[jira] [Commented] (EAGLE-717) Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-717:
--

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/596
  
@baibaichen what's the command you use for running it?


> Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly
> 
>
> Key: EAGLE-717
> URL: https://issues.apache.org/jira/browse/EAGLE-717
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Chang chen
>Assignee: Chang chen
>  Labels: unit-test
> Fix For: v0.5.0
>
>
> Eagle UT need load siddhi string extension dynamically, but the current 
> maven-surefire-plugin is too old (2.6), and  can't work correctly in always 
> forkMode which is needed for HBase UT. See [Class Loading and Forking in 
> Maven 
> Surefire|http://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html]
>  to understand how maven-surefire-plugin sets *java.class.path* and why.
>  



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

[jira] [Commented] (EAGLE-717) Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-717:
--

Github user baibaichen commented on the issue:

https://github.com/apache/incubator-eagle/pull/596
  
@haoch could you please merge this commit  so that we can take progress on 
UT coverage 


> Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly
> 
>
> Key: EAGLE-717
> URL: https://issues.apache.org/jira/browse/EAGLE-717
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Chang chen
>Assignee: Chang chen
>  Labels: unit-test
> Fix For: v0.5.0
>
>
> Eagle UT need load siddhi string extension dynamically, but the current 
> maven-surefire-plugin is too old (2.6), and  can't work correctly in always 
> forkMode which is needed for HBase UT. See [Class Loading and Forking in 
> Maven 
> Surefire|http://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html]
>  to understand how maven-surefire-plugin sets *java.class.path* and why.
>  



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

[jira] [Commented] (EAGLE-680) Can't generate Html coverage report

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-680:
--

Github user baibaichen commented on the issue:

https://github.com/apache/incubator-eagle/pull/559
  
@haoch could you please merge this commit  so that we can take progress on 
UT coverage 


> Can't generate Html coverage report 
> 
>
> Key: EAGLE-680
> URL: https://issues.apache.org/jira/browse/EAGLE-680
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Chang chen
>Assignee: Lingang Deng
> Fix For: v0.5.0
>
>
> The Current cobertura plugin just generate xml format by default which is 
> inconvenient  for local verification,



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

[GitHub] incubator-eagle issue #596: [EAGLE-717] Upgrade maven-surefire-plugin for su...

[baibaichen]

Github user baibaichen commented on the issue:

https://github.com/apache/incubator-eagle/pull/596
  
@haoch could you please merge this commit  so that we can take progress on 
UT coverage 


---
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 #559: EAGLE-680 Can't genetate Html coverage report

[baibaichen]

Github user baibaichen commented on the issue:

https://github.com/apache/incubator-eagle/pull/559
  
@haoch could you please merge this commit  so that we can take progress on 
UT coverage 


---
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-692) Modify HBaseAuditLogAppProvider.xml to integrate necessary and correct properties

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-692:
--

Github user chitin closed the pull request at:

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


> Modify HBaseAuditLogAppProvider.xml to integrate necessary and correct 
> properties
> -
>
> Key: EAGLE-692
> URL: https://issues.apache.org/jira/browse/EAGLE-692
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Lingang Deng
>Assignee: Lingang Deng
>Priority: Minor
> Fix For: v0.5.0
>
>




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

[GitHub] incubator-eagle pull request #572: EAGLE-692 Modify HBaseAuditLogAppProvider...

[chitin]

Github user chitin closed the pull request at:

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


---
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 branch-0.4 issue

[Yaung Ou]

dear eagle developers:
when the eagle-website and storm task run for a few hours and no one to
access,they all down. i found some error in the worker-6703.log,i list then
at the end of the email.
i am using mariadb,i set mariadb parameter `wait_timeout` a very large
number to figure out this issue.
sorry for my bad english,looking forward to reply,thx.

2016-10-28T00:42:40.805+0800 c.n.c.AbstractPollingScheduler [ERROR] Error
getting result from polling source
java.lang.IllegalStateException: java.lang.Exception: Got an exception when
query eagle service: java.io.IOException:
org.apache.torque.TorqueException:
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No
operations allowed after connection closed.
org.apache.eagle.storage.jdbc.JdbcStorage.query(JdbcStorage.java:179)
org.apache.eagle.storage.operation.QueryStatement.execute(QueryStatement.java:47)
org.apache.eagle.service.generic.GenericEntityServiceResource.search(GenericEntityServiceResource.java:443)
sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:606)
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)

at
org.apache.eagle.policy.dao.PolicyDefinitionEntityDAOImpl.findActivePolicies(PolicyDefinitionEntityDAOImpl.java:74)
~[eagle-policy-base-0.4.0-incubating.jar:0.4.0-incubating]
at
org.apache.eagle.policy.dao.PolicyDefinitionEntityDAOImpl.findActivePoliciesGroupbyExecutorId(PolicyDefinitionEntityDAOImpl.java:83)
~[eagle-policy-base-0.4.0-incubating.jar:0.4.0-incubating]
at
org.apache.eagle.policy.DynamicPolicyLoader$DynamicPolicySource.poll(DynamicPolicyLoader.java:191)
~[eagle-policy-base-0.4.0-incubating.jar:0.4.0-incubating]
at
com.netflix.config.AbstractPollingScheduler$1.run(AbstractPollingScheduler.java:163)
~[archaius-core-0.6.1.jar:na]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
[na:1.7.0_79]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
[na:1.7.0_79]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
[na:1.7.0_79]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
[na:1.7.0_79]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[na:1.7.0_79]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[na:1.7.0_79]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_79]
Caused by: java.lang.Exception: Got an exception when query eagle service:
java.io.IOException: org.apache.torque.TorqueException:
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No
operations allowed after connection closed.
org.apache.eagle.storage.jdbc.JdbcStorage.query(JdbcStorage.java:179)
org.apache.eagle.storage.operation.QueryStatement.execute(QueryStatement.java:47)
org.apache.eagle.service.generic.GenericEntityServiceResource.search(GenericEntityServiceResource.java:443)
sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:606)
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)

at
org.apache.eagle.policy.dao.PolicyDefinitionEntityDAOImpl.findActivePolicies(PolicyDefinitionEntityDAOImpl.java:63)
~[eagle-policy-base-0.4.0-incubating.jar:0.4.0-incubating]
... 10 common frames omitted

[jira] [Resolved] (EAGLE-706) Policy UI adv mode support sql highlight

[Jilin, Jiang (JIRA)]

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

Jilin, Jiang resolved EAGLE-706.

Resolution: Fixed

> Policy UI adv mode support sql highlight
> 
>
> Key: EAGLE-706
> URL: https://issues.apache.org/jira/browse/EAGLE-706
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Jilin, Jiang
>Assignee: Jilin, Jiang
>Priority: Minor
> Fix For: v0.5.0
>
>




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

[jira] [Created] (EAGLE-719) configuration bug in applications

[wujinhu (JIRA)]

wujinhu created EAGLE-719:
-

 Summary: configuration bug in applications
 Key: EAGLE-719
 URL: https://issues.apache.org/jira/browse/EAGLE-719
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: wujinhu
Assignee: Michael Wu
 Fix For: v0.5.0


In 
eagle-hadoop-queue/eagle-jpm-mr-history/eagle-jpm-mr-running/eagle-jpm-spark-history/eagle-jpm-aggregation
 applications, there is an xxxAppConfig class in each application. But they 
have a static member like manager, which could not initialize twice

public static Config getInstance(Config config) {
if (config != null && manager.config == null) {
manager.init(config);
}
return manager;
}

But we have many sites in production,  and will call method getInstance many 
times. So it will cause we may get the configuration of first site for 
remaining sites.



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

[jira] [Commented] (EAGLE-716) [API] Validate before saving policy

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-716:
--

Github user asfgit closed the pull request at:

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


> [API] Validate before saving policy
> ---
>
> Key: EAGLE-716
> URL: https://issues.apache.org/jira/browse/EAGLE-716
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> [API] Forcefully Validate before saving policy into metadata when calling 
> {code}
> POST /policies
> {code}



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

[jira] [Resolved] (EAGLE-683) AlertEngine : Improve metadata store performance

[Su Ralph (JIRA)]

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

Su Ralph resolved EAGLE-683.

Resolution: Fixed

close as merged

> AlertEngine : Improve metadata store performance
> 
>
> Key: EAGLE-683
> URL: https://issues.apache.org/jira/browse/EAGLE-683
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Zeng, Bryant
> Fix For: v0.5.0
>
>
> Currently, we enable periodically schedule in coordinator service itself. If 
> this is enabled, the schedule spec will finally used up metadata storage.
> We should
> 1. Disable periodically schedule by default (storage like mysql doesn't have 
> capped feature)
> 2. For mongodb storage, use capped collection for schedule_specs, 
> policy_snapshots, streamSnapshots, groupSpecs, alertSpecs, monitoredStreams, 
> spoutSpecs (all schedule spec related collection).
> Let use default config of 20,000 as capped collection size.



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

[GitHub] incubator-eagle pull request #593: [EAGLE-716][API] Forcefully Validate befo...

[asfgit]

Github user asfgit closed the pull request at:

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


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

Podling Report Reminder - November 2016

[johndament]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 16 November 2016, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, November 02).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.

This should be appended to the Incubator Wiki page at:

http://wiki.apache.org/incubator/November2016

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

[jira] [Updated] (EAGLE-452) Add Jersey Resource Unit Test Case

[Chang chen (JIRA)]

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

Chang chen updated EAGLE-452:
-
Labels: unit-test  (was: )

> Add Jersey Resource Unit Test Case
> --
>
> Key: EAGLE-452
> URL: https://issues.apache.org/jira/browse/EAGLE-452
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.4.0, v0.5.0
>Reporter: Hao Chen
>Assignee: Chang chen
>Priority: Minor
>  Labels: unit-test
> Fix For: v0.5.0
>
>
> We need to add more Unit Test Cases for Jersey Resources, referring to
> https://github.com/apache/incubator-eagle/blob/develop/eagle-examples/eagle-app-example/src/test/java/org/apache/eagle/app/example/ExampleApplicationProviderTest.java#L45



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

[jira] [Updated] (EAGLE-717) Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly

[Chang chen (JIRA)]

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

Chang chen updated EAGLE-717:
-
Labels: unit-test  (was: )

> Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly
> 
>
> Key: EAGLE-717
> URL: https://issues.apache.org/jira/browse/EAGLE-717
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Chang chen
>Assignee: Chang chen
>  Labels: unit-test
> Fix For: v0.5.0
>
>
> Eagle UT need load siddhi string extension dynamically, but the current 
> maven-surefire-plugin is too old (2.6), and  can't work correctly in always 
> forkMode which is needed for HBase UT. See [Class Loading and Forking in 
> Maven 
> Surefire|http://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html]
>  to understand how maven-surefire-plugin sets *java.class.path* and why.
>  



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

[GitHub] incubator-eagle issue #595: Eagle 717

[baibaichen]

Github user baibaichen commented on the issue:

https://github.com/apache/incubator-eagle/pull/595
  
I already closed it,  and created a new PR 
https://github.com/apache/incubator-eagle/pull/596


---
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 #595: Eagle 717

[haoch]

Github user haoch commented on the issue:

https://github.com/apache/incubator-eagle/pull/595
  
Hi Chang @baibaichen , it seems that this PR includes lots of expected 
changes, could you please help confirm 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.
---

[jira] [Closed] (EAGLE-692) Modify HBaseAuditLogAppProvider.xml to integrate necessary and correct properties

[Lingang Deng (JIRA)]

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

Lingang Deng closed EAGLE-692.
--
Resolution: Duplicate

> Modify HBaseAuditLogAppProvider.xml to integrate necessary and correct 
> properties
> -
>
> Key: EAGLE-692
> URL: https://issues.apache.org/jira/browse/EAGLE-692
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Lingang Deng
>Assignee: Lingang Deng
>Priority: Minor
> Fix For: v0.5.0
>
>




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

[jira] [Commented] (EAGLE-717) Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-717:
--

GitHub user baibaichen opened a pull request:

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

[EAGLE-717] Upgrade maven-surefire-plugin for supporting forkMode ( =…



Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

 - [ ] Make sure the PR title is formatted like:
   `[EAGLE-] Description of pull request`
 - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
   Travis-CI on your fork and ensure the whole test matrix passes).
 - [ ] Replace `` in the title with the actual Jira issue
   number, if there is one.
 - [ ] If this contribution is large, please file an Apache
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.txt).

---
… always ) correctly

Upgrade maven-surefire-plugin to 2.19.1 (latest version)

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

$ git pull https://github.com/baibaichen/incubator-eagle EAGLE-717

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

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


commit a541e4921ef3fdc36c1b1fe22ea4180d376d506d
Author: baibaichen 
Date:   2016-11-01T11:02:29Z

[EAGLE-717] Upgrade maven-surefire-plugin for supporting forkMode ( = 
always ) correctly

Upgrade maven-surefire-plugin to 2.19.1 (latest version)




> Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly
> 
>
> Key: EAGLE-717
> URL: https://issues.apache.org/jira/browse/EAGLE-717
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Chang chen
>Assignee: Chang chen
> Fix For: v0.5.0
>
>
> Eagle UT need load siddhi string extension dynamically, but the current 
> maven-surefire-plugin is too old (2.6), and  can't work correctly in always 
> forkMode which is needed for HBase UT. See [Class Loading and Forking in 
> Maven 
> Surefire|http://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html]
>  to understand how maven-surefire-plugin sets *java.class.path* and why.
>  



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

[GitHub] incubator-eagle pull request #596: [EAGLE-717] Upgrade maven-surefire-plugin...

[baibaichen]

GitHub user baibaichen opened a pull request:

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

[EAGLE-717] Upgrade maven-surefire-plugin for supporting forkMode ( =…



Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

 - [ ] Make sure the PR title is formatted like:
   `[EAGLE-] Description of pull request`
 - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
   Travis-CI on your fork and ensure the whole test matrix passes).
 - [ ] Replace `` in the title with the actual Jira issue
   number, if there is one.
 - [ ] If this contribution is large, please file an Apache
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.txt).

---
… always ) correctly

Upgrade maven-surefire-plugin to 2.19.1 (latest version)

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

$ git pull https://github.com/baibaichen/incubator-eagle EAGLE-717

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

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


commit a541e4921ef3fdc36c1b1fe22ea4180d376d506d
Author: baibaichen 
Date:   2016-11-01T11:02:29Z

[EAGLE-717] Upgrade maven-surefire-plugin for supporting forkMode ( = 
always ) correctly

Upgrade maven-surefire-plugin to 2.19.1 (latest version)




---
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 #595: Eagle 717

[baibaichen]

Github user baibaichen closed the pull request at:

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


---
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 #595: Eagle 717

[baibaichen]

GitHub user baibaichen opened a pull request:

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

Eagle 717



Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

 - [ ] Make sure the PR title is formatted like:
   `[EAGLE-] Description of pull request`
 - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
   Travis-CI on your fork and ensure the whole test matrix passes).
 - [ ] Replace `` in the title with the actual Jira issue
   number, if there is one.
 - [ ] If this contribution is large, please file an Apache
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.txt).

---

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

$ git pull https://github.com/baibaichen/incubator-eagle EAGLE-717

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

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


commit 2f724c4e7b294670e5adb0b4690d0d48fa95b4cb
Author: mizeng 
Date:   2016-10-26T06:22:33Z

EAGLE-683: Improve metadata store performance

Currently, we enable periodically schedule in coordinator service itself.
If this is enabled, the schedule spec will finally used up metadata storage.

So we need to improve metadata store performance by:
1. Disable periodically schedule by default (storage like mysql doesn't 
have capped feature).
2. For mongodb storage, use capped collection for schedule_specs, 
policy_snapshots,
streamSnapshots, groupSpecs, alertSpecs, monitoredStreams, spoutSpecs (all 
schedule spec related collection).

Author: Zeng, Bryant
Reviewer: ralphsu

This closes #566

commit e4f41f2e87d17b92d5abf110440569381853a46c
Author: wujinhu 
Date:   2016-10-27T07:45:41Z

[EAGLE-659] mr history feeder integrate with alert engine

Author: wujinhu 

Closes #571 from wujinhu/EAGLE-659.

commit 7173f2e73424b1d06aaa4a4ec9f5c2d8dbf2ae3e
Author: zombieJ 
Date:   2016-10-27T08:13:26Z

[EAGLE-686] UI add site select on top nav bar

UI add site select on top nav bar for user quick access.

Author: zombieJ 

Closes #569 from zombieJ/EAGLE-686.

commit 853d92a01cde25a34ede48c6f070d76e1d1d19a1
Author: Zhao, Qingwen 
Date:   2016-10-27T10:31:04Z

[EAGLE-681] Add new publisher AlertEagleStorePlugin

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

Author: Zhao, Qingwen 

Closes #573 from qingwen220/EAGLE-681.

commit 8418497769e022c79b7fa67895b34ef23fe35a2d
Author: Zhao, Qingwen 
Date:   2016-10-28T02:10:50Z

[MINOR] Enhance new publisher AlertEagleStorePlugin

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

* implement alert apis on jdbc & mongodb
* add a rest api for searching a alert by alertId

Author: Zhao, Qingwen 

Closes #575 from qingwen220/EAGLE-681.

commit b93d23c651a5ced46ce149bdb530d7ab79c459ca
Author: zombieJ 
Date:   2016-10-28T06:29:43Z

[EAGLE-688] UI support Alert display

For backend will provide the alert api. UI will also support it.

Author: zombieJ 

Closes #576 from zombieJ/EAGLE-688.

commit 5ca0dc090a58c285b13f61559ae006ffc0730221
Author: wujinhu 
Date:   2016-10-28T06:54:51Z

[EAGLE-694] alert engine could not reduce alert bolt number when 
parallelism of p…

Author: wujinhu 

Closes #577 from wujinhu/EAGLE-694.

commit 7eaf972d2c4d6e3cff488a174cf0ef3c00deb5e2
Author: anyway1021 
Date:   2016-10-28T07:40:40Z

[EAGLE-695] fetching hadoop.cluster.allocatedvirtualcores instead of 
hadoop.cluster.totalvirtualcores

Virtual Core related metrics are additional, starting from hadoop version 
2.7.x. And we were originally fetching hadoop.cluster.allocatedvirtualcores. 
Now it seems that hadoop.cluster.totalvirtualcores is more meaningful. So 
change code to fetch and show it up in hadoop-queue monitoring application.

Author: anyway1021 

Closes #574 from anyway1021/EAGLE-695.

commit 19afb0754f3c244193c91d718e7f28d3b79a8283
Author: anyway1021 
Date:   2016-10-28T07:43:01Z

[EAGLE-697] fix wrong url-concatenation for monitoring hadoop queue

For hadoop queue monitoring, when endpoint url doesn't end with a slash, 
the final url will be composed by concatenating endpoint directly with resource 
path. E.g.
endpoint: https://a.b.c:
resource path: ws/v1/cluster/some
Then final url is: https://a.b.c:ws/v1/cluster/some, which make 
application fail.
We should add "/" to existing constants of resource paths, and compose 
final url with utils.
Besides, add concrete unit test to guarantee this part functions normally.

Author: anyway1021 
   

[GitHub] incubator-eagle pull request #594: adjust description of dataSourceConfig.rM...

[anyway1021]

GitHub user anyway1021 opened a pull request:

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

adjust description of dataSourceConfig.rMEndPoints in 
hadoop-queue-monitoring

Trivial modification, didn't open jira ticket for it.

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

$ git pull https://github.com/anyway1021/incubator-eagle adjust-desc

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

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


commit 1fb55621a706afd9b6e98b7eef936e1844eeec99
Author: anyway1021 
Date:   2016-11-01T10:32:21Z

adjust description of dataSourceConfig.rMEndPoints in 
hadoop-queue-monitoring




---
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-718) let hadoop queue monitoring application accept namenode url list separated by comma

[Michael Wu (JIRA)]

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

Michael Wu closed EAGLE-718.

Resolution: Not A Problem

Already recognize multiple urls separated by comma, no need to change code, 
close this task.

> let hadoop queue monitoring application accept namenode url list separated by 
> comma
> ---
>
> Key: EAGLE-718
> URL: https://issues.apache.org/jira/browse/EAGLE-718
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>
> Except for monitoring main resource manager, we have to keep an eye on 
> secondary one, in case name node is switched for HA reason.



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

[jira] [Updated] (EAGLE-718) let hadoop queue monitoring application accept namenode url list separated by comma

[Michael Wu (JIRA)]

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

Michael Wu updated EAGLE-718:
-
Description: Except for monitoring main resource manager, we have to keep 
an eye on secondary one, in case name node is switched for HA reason.  (was: 
Except for monitoring main name node, we have to keep an eye on secondary name 
node, in case name node is switched for HA reason.)

> let hadoop queue monitoring application accept namenode url list separated by 
> comma
> ---
>
> Key: EAGLE-718
> URL: https://issues.apache.org/jira/browse/EAGLE-718
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>
> Except for monitoring main resource manager, we have to keep an eye on 
> secondary one, in case name node is switched for HA reason.



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

[jira] [Resolved] (EAGLE-714) Application improvement

[Jilin, Jiang (JIRA)]

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

Jilin, Jiang resolved EAGLE-714.

Resolution: Fixed

> Application improvement
> ---
>
> Key: EAGLE-714
> URL: https://issues.apache.org/jira/browse/EAGLE-714
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Jilin, Jiang
>Assignee: Jilin, Jiang
>Priority: Critical
> Fix For: v0.5.0
>
>
> * Application detail page display as `N/A`
> * use 2 line of input field (jarPath)



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

[jira] [Closed] (EAGLE-708) document the Apache Eagle deployment from scratch

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-708.
-
Resolution: Resolved

> document the Apache Eagle deployment from scratch
> -
>
> Key: EAGLE-708
> URL: https://issues.apache.org/jira/browse/EAGLE-708
> Project: Eagle
>  Issue Type: Task
>Reporter: jianzhong.chen
>Assignee: wujinhu
>  Labels: documentation
> Fix For: v0.5.0
>
>
> We should have a documentation about how to setup an Apache Eagle environment 
> from scratch, the OS and its configuration, the external dependencies, 
> versions, configuration, ..



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

[GitHub] incubator-eagle pull request #589: Eagle-714 Application improvement

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-718) let hadoop queue monitoring application accept namenode url list separated by comma

[Michael Wu (JIRA)]

Michael Wu created EAGLE-718:


 Summary: let hadoop queue monitoring application accept namenode 
url list separated by comma
 Key: EAGLE-718
 URL: https://issues.apache.org/jira/browse/EAGLE-718
 Project: Eagle
  Issue Type: Task
Reporter: Michael Wu
Assignee: Michael Wu


Except for monitoring main name node, we have to keep an eye on secondary name 
node, in case name node is switched for HA reason.



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

[jira] [Updated] (EAGLE-717) Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly

[Chang chen (JIRA)]

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

Chang chen updated EAGLE-717:
-
Description: 
Eagle UT need load siddhi string extension dynamically, but the current 
maven-surefire-plugin is too old (2.6), and  can't work correctly in always 
forkMode which is needed for HBase UT. See [Class Loading and Forking in Maven 
Surefire|http://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html]
 to understand how maven-surefire-plugin sets *java.class.path* and why.

 



  was:
Eagle UT need load siddhi string extension dynamically, but the current 
maven-surefire-plugin is too old (2.6), and  can't work correctly in always 
forkMode which is needed for HBase UT. See [Class Loading and Forking in Maven 
Surefire|http://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html]
 to understand how maven-surefire-plugin set java.class.path and why.

 




> Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly
> 
>
> Key: EAGLE-717
> URL: https://issues.apache.org/jira/browse/EAGLE-717
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Chang chen
>Assignee: Chang chen
> Fix For: v0.5.0
>
>
> Eagle UT need load siddhi string extension dynamically, but the current 
> maven-surefire-plugin is too old (2.6), and  can't work correctly in always 
> forkMode which is needed for HBase UT. See [Class Loading and Forking in 
> Maven 
> Surefire|http://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html]
>  to understand how maven-surefire-plugin sets *java.class.path* and why.
>  



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

[jira] [Created] (EAGLE-717) Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly

[Chang chen (JIRA)]

Chang chen created EAGLE-717:


 Summary: Upgrade maven-surefire-plugin for supporting forkMode ( = 
always ) correctly
 Key: EAGLE-717
 URL: https://issues.apache.org/jira/browse/EAGLE-717
 Project: Eagle
  Issue Type: Sub-task
Affects Versions: v0.5.0
Reporter: Chang chen
 Fix For: v0.5.0


Eagle UT need load siddhi string extension dynamically, but the current 
maven-surefire-plugin is too old (2.6), and  can't work correctly in always 
forkMode which is needed for HBase UT. See [Class Loading and Forking in Maven 
Surefire|http://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html]
 to understand how maven-surefire-plugin set java.class.path and why.

 





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

[jira] [Assigned] (EAGLE-717) Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly

[Chang chen (JIRA)]

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

Chang chen reassigned EAGLE-717:


Assignee: Chang chen

> Upgrade maven-surefire-plugin for supporting forkMode ( = always ) correctly
> 
>
> Key: EAGLE-717
> URL: https://issues.apache.org/jira/browse/EAGLE-717
> Project: Eagle
>  Issue Type: Sub-task
>Affects Versions: v0.5.0
>Reporter: Chang chen
>Assignee: Chang chen
> Fix For: v0.5.0
>
>
> Eagle UT need load siddhi string extension dynamically, but the current 
> maven-surefire-plugin is too old (2.6), and  can't work correctly in always 
> forkMode which is needed for HBase UT. See [Class Loading and Forking in 
> Maven 
> Surefire|http://maven.apache.org/surefire/maven-surefire-plugin/examples/class-loading.html]
>  to understand how maven-surefire-plugin set java.class.path and why.
>  



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

[jira] [Commented] (EAGLE-716) [API] Validate before saving policy

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-716:
--

GitHub user haoch opened a pull request:

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

[EAGLE-716][API] Forcefully Validate before saving policy into metadata

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

[API] Forcefully Validate before saving policy into metadata when calling 

POST /policies


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

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

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

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


commit 5bf8e415773589034b06d47446d968cf5d931018
Author: Hao Chen 
Date:   2016-11-01T09:53:55Z

[API] Forcefully Validate before saving policy into metadata when calling




> [API] Validate before saving policy
> ---
>
> Key: EAGLE-716
> URL: https://issues.apache.org/jira/browse/EAGLE-716
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> [API] Forcefully Validate before saving policy into metadata when calling 
> {code}
> POST /policies
> {code}



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

[jira] [Commented] (EAGLE-690) Integrate topology health check with alert engine

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-690:
--

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r8591
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/resources/application.conf ---
@@ -28,7 +32,7 @@
   }
 
   dataSourceConfig : {
-hdfs.namenodeUrl: "http://sandbox.hortonworks.com:50070";,
+hdfs.namenodeUrl: "https://apollo-phx-nn.vip.ebay.com:50070";,
--- End diff --

please remove this sensitive info!


> Integrate topology health check with alert engine
> -
>
> Key: EAGLE-690
> URL: https://issues.apache.org/jira/browse/EAGLE-690
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
> Fix For: v0.5.0
>
>
> Integrate topology health check with alert engine.
> It will send timestamp,tag,status to alert engine,when the node status is 
> dead, alert engine will send the email to user



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

[jira] [Commented] (EAGLE-690) Integrate topology health check with alert engine

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-690:
--

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r85900118
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/resources/application.conf ---
@@ -41,10 +45,21 @@
   }
 },
 mr: {
-  rmUrl: "http://sandbox.hortonworks.com:8088";,
+  rmUrl: "https://apollo-phx-rm-2.vip.ebay.com:50030";,
   historyServerUrl : "http://sandbox.hortonworks.com:19888";  #if not 
need, then empty
 }
   }
+  
+  "dataSinkConfig": {
+"topic" : "topology_health_check",
+"brokerList" : "sandbox.hortonworks.com:6667",
+"serializerClass" : "kafka.serializer.StringEncoder",
+"keySerializerClass" : "kafka.serializer.StringEncoder"
+"producerType" : "async",
+"numBatchMessages" : "4096",
+"maxQueueBufferMs" : "5000",
+"requestRequiredAcks" : "0"
+  }
 
   eagleProps : {
--- End diff --

please update the service configurations in this file as well


> Integrate topology health check with alert engine
> -
>
> Key: EAGLE-690
> URL: https://issues.apache.org/jira/browse/EAGLE-690
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
> Fix For: v0.5.0
>
>
> Integrate topology health check with alert engine.
> It will send timestamp,tag,status to alert engine,when the node status is 
> dead, alert engine will send the email to user



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

[jira] [Commented] (EAGLE-690) Integrate topology health check with alert engine

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-690:
--

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r85900047
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/resources/application.conf ---
@@ -41,10 +45,21 @@
   }
 },
 mr: {
-  rmUrl: "http://sandbox.hortonworks.com:8088";,
+  rmUrl: "https://apollo-phx-rm-2.vip.ebay.com:50030";,
--- End diff --

please remove this sensitive data


> Integrate topology health check with alert engine
> -
>
> Key: EAGLE-690
> URL: https://issues.apache.org/jira/browse/EAGLE-690
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: yupu
>Assignee: yupu
>  Labels: features
> Fix For: v0.5.0
>
>
> Integrate topology health check with alert engine.
> It will send timestamp,tag,status to alert engine,when the node status is 
> dead, alert engine will send the email to user



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

[GitHub] incubator-eagle pull request #570: EAGLE-690 : integrage topology health che...

[qingwen220]

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r85900118
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/resources/application.conf ---
@@ -41,10 +45,21 @@
   }
 },
 mr: {
-  rmUrl: "http://sandbox.hortonworks.com:8088";,
+  rmUrl: "https://apollo-phx-rm-2.vip.ebay.com:50030";,
   historyServerUrl : "http://sandbox.hortonworks.com:19888";  #if not 
need, then empty
 }
   }
+  
+  "dataSinkConfig": {
+"topic" : "topology_health_check",
+"brokerList" : "sandbox.hortonworks.com:6667",
+"serializerClass" : "kafka.serializer.StringEncoder",
+"keySerializerClass" : "kafka.serializer.StringEncoder"
+"producerType" : "async",
+"numBatchMessages" : "4096",
+"maxQueueBufferMs" : "5000",
+"requestRequiredAcks" : "0"
+  }
 
   eagleProps : {
--- End diff --

please update the service configurations in this file 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.
---

[GitHub] incubator-eagle pull request #570: EAGLE-690 : integrage topology health che...

[qingwen220]

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r85900047
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/resources/application.conf ---
@@ -41,10 +45,21 @@
   }
 },
 mr: {
-  rmUrl: "http://sandbox.hortonworks.com:8088";,
+  rmUrl: "https://apollo-phx-rm-2.vip.ebay.com:50030";,
--- End diff --

please remove this sensitive data


---
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 #593: [EAGLE-716][API] Forcefully Validate befo...

[haoch]

GitHub user haoch opened a pull request:

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

[EAGLE-716][API] Forcefully Validate before saving policy into metadata

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

[API] Forcefully Validate before saving policy into metadata when calling 

POST /policies


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

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

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

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


commit 5bf8e415773589034b06d47446d968cf5d931018
Author: Hao Chen 
Date:   2016-11-01T09:53:55Z

[API] Forcefully Validate before saving policy into metadata when calling




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

[GitHub] incubator-eagle pull request #570: EAGLE-690 : integrage topology health che...

[qingwen220]

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

https://github.com/apache/incubator-eagle/pull/570#discussion_r8591
  
--- Diff: 
eagle-topology-check/eagle-topology-app/src/main/resources/application.conf ---
@@ -28,7 +32,7 @@
   }
 
   dataSourceConfig : {
-hdfs.namenodeUrl: "http://sandbox.hortonworks.com:50070";,
+hdfs.namenodeUrl: "https://apollo-phx-nn.vip.ebay.com:50070";,
--- End diff --

please remove this sensitive info!


---
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-716) [API] Validate before saving policy

[Hao Chen (JIRA)]

Hao Chen created EAGLE-716:
--

 Summary: [API] Validate before saving policy
 Key: EAGLE-716
 URL: https://issues.apache.org/jira/browse/EAGLE-716
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.5.0


[API] Forcefully Validate before saving policy into metadata when calling 
{code}
POST /policies
{code}



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

[jira] [Commented] (EAGLE-692) Modify HBaseAuditLogAppProvider.xml to integrate necessary and correct properties

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-692:
--

Github user qingwen220 commented on the issue:

https://github.com/apache/incubator-eagle/pull/572
  
Hi chitin,

This ticket has been done in another pull request. You can close this one. 
Thanks!


> Modify HBaseAuditLogAppProvider.xml to integrate necessary and correct 
> properties
> -
>
> Key: EAGLE-692
> URL: https://issues.apache.org/jira/browse/EAGLE-692
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Lingang Deng
>Assignee: Lingang Deng
>Priority: Minor
> Fix For: v0.5.0
>
>




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

[GitHub] incubator-eagle issue #589: Eagle-714 Application improvement

[qingwen220]

Github user qingwen220 commented on the issue:

https://github.com/apache/incubator-eagle/pull/589
  
LGTM


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

[GitHub] incubator-eagle issue #572: EAGLE-692 Modify HBaseAuditLogAppProvider.xml to...

[qingwen220]

Github user qingwen220 commented on the issue:

https://github.com/apache/incubator-eagle/pull/572
  
Hi chitin,

This ticket has been done in another pull request. You can close this one. 
Thanks!


---
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 #592: [EAGLE-715] optimize some configurations ...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[jira] [Closed] (EAGLE-715) optimize some configurations for alert

[wujinhu (JIRA)]

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

wujinhu closed EAGLE-715.
-
Resolution: Fixed

> optimize some configurations for alert
> --
>
> Key: EAGLE-715
> URL: https://issues.apache.org/jira/browse/EAGLE-715
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> optimize some configurations for alert



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

[jira] [Commented] (EAGLE-715) optimize some configurations for alert

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on EAGLE-715:
--

Github user asfgit closed the pull request at:

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


> optimize some configurations for alert
> --
>
> Key: EAGLE-715
> URL: https://issues.apache.org/jira/browse/EAGLE-715
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> optimize some configurations for alert



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