[jira] [Commented] (EAGLE-924) urls to healthy and unhealthy region-servers in hbase dashboard is not accurate enough
[ https://issues.apache.org/jira/browse/EAGLE-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880063#comment-15880063 ] ASF GitHub Bot commented on EAGLE-924: -- GitHub user chitin opened a pull request: https://github.com/apache/eagle/pull/840 [EAGLE-924]urls to healthy and unhealthy region-servers in hbase dashboard is not accurate enough [EAGLE-924]urls to healthy and unhealthy region-servers in hbase dashboard is not accurate enough - Add status filter in web url,append "?status=healthy" or "?status=unhealthy" to the url - Fix exception when we change time interval - Fix dashboard show when no data and exception. https://issues.apache.org/jira/browse/EAGLE-924 You can merge this pull request into a Git repository by running: $ git pull https://github.com/chitin/eagle eagle924 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/840.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 #840 commit 62ab13d3198497925bd7f54e52f04ca788b0e1ad Author: chitin Date: 2017-02-23T07:42:42Z [EAGLE-924] urls to healthy and unhealthy region-servers in hbase dashboard is not accurate enough - Add status filter in web url,append "?status=healthy" or "?status=unhealthy" to the url - Fix exception when we change time interval - Fix dashboard show when no data and exception. https://issues.apache.org/jira/browse/EAGLE-924 > urls to healthy and unhealthy region-servers in hbase dashboard is not > accurate enough > -- > > Key: EAGLE-924 > URL: https://issues.apache.org/jira/browse/EAGLE-924 > Project: Eagle > Issue Type: Bug > Components: App::Hadoop JMX Monitor >Affects Versions: v0.5.0 >Reporter: Michael Wu >Assignee: Lingang Deng > Fix For: v0.6.0 > > Attachments: Screen Shot 2017-02-22 at 16.24.09.png > > > Issue: In hbase dashboard of a site, in the top section, there are 2 links > referring to urls of healthy and unhealthy region-server lists. But > currently, when people click the link, the page is directed to a full list of > all region-servers, not the corresponding healthy-list or unhealthy-list. > Suggestion: we can add some filter in the url, for example, append > "?status=healthy" or "?status=unhealthy" to the url, and update the link with > new urls. > Please see the screenshot in the attachment of this ticket. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #840: [EAGLE-924]urls to healthy and unhealthy region-ser...
GitHub user chitin opened a pull request: https://github.com/apache/eagle/pull/840 [EAGLE-924]urls to healthy and unhealthy region-servers in hbase dashboard is not accurate enough [EAGLE-924]urls to healthy and unhealthy region-servers in hbase dashboard is not accurate enough - Add status filter in web url,append "?status=healthy" or "?status=unhealthy" to the url - Fix exception when we change time interval - Fix dashboard show when no data and exception. https://issues.apache.org/jira/browse/EAGLE-924 You can merge this pull request into a Git repository by running: $ git pull https://github.com/chitin/eagle eagle924 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/840.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 #840 commit 62ab13d3198497925bd7f54e52f04ca788b0e1ad Author: chitin Date: 2017-02-23T07:42:42Z [EAGLE-924] urls to healthy and unhealthy region-servers in hbase dashboard is not accurate enough - Add status filter in web url,append "?status=healthy" or "?status=unhealthy" to the url - Fix exception when we change time interval - Fix dashboard show when no data and exception. https://issues.apache.org/jira/browse/EAGLE-924 --- 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-927) add jmx resource info to Hadoop JMX Monitor
[
https://issues.apache.org/jira/browse/EAGLE-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879953#comment-15879953
]
ASF GitHub Bot commented on EAGLE-927:
--
Github user haoch commented on a diff in the pull request:
https://github.com/apache/eagle/pull/839#discussion_r102645205
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-common/src/test/java/org/apache/eagle/siddhiext/StringSubtractFunctionExtensionTest.java
---
@@ -0,0 +1,62 @@
+/*
+ * 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.siddhiext;
+
+import org.junit.*;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+import org.wso2.siddhi.core.ExecutionPlanRuntime;
+import org.wso2.siddhi.core.SiddhiManager;
+import org.wso2.siddhi.core.event.Event;
+import org.wso2.siddhi.core.stream.input.InputHandler;
+import org.wso2.siddhi.core.stream.output.StreamCallback;
+import org.wso2.siddhi.core.util.EventPrinter;
+
+public class StringSubtractFunctionExtensionTest {
+private static final Logger LOG =
LoggerFactory.getLogger(StringSubtractFunctionExtensionTest.class);
+
+@Test
+public void testStringSubtract() throws Exception {
+String ql = " define stream log(timestamp long, switchLabel
string, port string, message string); " +
+" from log select string:subtract(\"a:b:c:d:e:f:g\",
\"g:a:e:d:z:r:s:c\") as alertKey insert into output; ";
+SiddhiManager manager = new SiddhiManager();
+ExecutionPlanRuntime runtime =
manager.createExecutionPlanRuntime(ql);
+runtime.addCallback("output", new StreamCallback() {
+@Override
+public void receive(Event[] events) {
+EventPrinter.print(events);
+Assert.assertTrue(events.length == 1);
+
Assert.assertTrue(events[0].getData(0).toString().equals("z\nr\ns"));
+}
+});
+
+runtime.start();
+
+InputHandler logInput = runtime.getInputHandler("log");
+
+Event e = new Event();
+e.setTimestamp(System.currentTimeMillis());
+e.setData(new Object[] {System.currentTimeMillis(),
"switch-ra-slc-01", "port01", "log-message"});
--- End diff --
Remove sensitive info
> add jmx resource info to Hadoop JMX Monitor
> ---
>
> Key: EAGLE-927
> URL: https://issues.apache.org/jira/browse/EAGLE-927
> Project: Eagle
> Issue Type: Improvement
> Components: App::Hadoop JMX Monitor
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> We need add an stream(HADOOP_JMX_RESOURCE_STREAM) to stand for jmx resource
> like corrupt files and live nodes and so on. For example, when we found
> missing block number via HADOOP_JMX_METRIC_STREAM by define a policy, we can
> find missing block id via HADOOP_JMX_RESOURCE_STREAM
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] eagle pull request #839: [EAGLE-927] support for hadoop jmx resource info
Github user haoch commented on a diff in the pull request:
https://github.com/apache/eagle/pull/839#discussion_r102645230
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-common/src/test/java/org/apache/eagle/siddhiext/StringSubtractFunctionExtensionTest.java
---
@@ -0,0 +1,62 @@
+/*
+ * 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.siddhiext;
+
+import org.junit.*;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+import org.wso2.siddhi.core.ExecutionPlanRuntime;
+import org.wso2.siddhi.core.SiddhiManager;
+import org.wso2.siddhi.core.event.Event;
+import org.wso2.siddhi.core.stream.input.InputHandler;
+import org.wso2.siddhi.core.stream.output.StreamCallback;
+import org.wso2.siddhi.core.util.EventPrinter;
+
+public class StringSubtractFunctionExtensionTest {
+private static final Logger LOG =
LoggerFactory.getLogger(StringSubtractFunctionExtensionTest.class);
+
+@Test
+public void testStringSubtract() throws Exception {
+String ql = " define stream log(timestamp long, switchLabel
string, port string, message string); " +
+" from log select string:subtract(\"a:b:c:d:e:f:g\",
\"g:a:e:d:z:r:s:c\") as alertKey insert into output; ";
+SiddhiManager manager = new SiddhiManager();
+ExecutionPlanRuntime runtime =
manager.createExecutionPlanRuntime(ql);
+runtime.addCallback("output", new StreamCallback() {
+@Override
+public void receive(Event[] events) {
+EventPrinter.print(events);
+Assert.assertTrue(events.length == 1);
+
Assert.assertTrue(events[0].getData(0).toString().equals("z\nr\ns"));
+}
+});
+
+runtime.start();
+
+InputHandler logInput = runtime.getInputHandler("log");
+
+Event e = new Event();
+e.setTimestamp(System.currentTimeMillis());
+e.setData(new Object[] {System.currentTimeMillis(),
"switch-ra-slc-01", "port01", "log-message"});
+logInput.send(e);
+
+Thread.sleep(1000);
--- End diff --
Avoid sleep in CEP ut
---
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-927) add jmx resource info to Hadoop JMX Monitor
[
https://issues.apache.org/jira/browse/EAGLE-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879952#comment-15879952
]
ASF GitHub Bot commented on EAGLE-927:
--
Github user haoch commented on a diff in the pull request:
https://github.com/apache/eagle/pull/839#discussion_r102645230
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-common/src/test/java/org/apache/eagle/siddhiext/StringSubtractFunctionExtensionTest.java
---
@@ -0,0 +1,62 @@
+/*
+ * 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.siddhiext;
+
+import org.junit.*;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+import org.wso2.siddhi.core.ExecutionPlanRuntime;
+import org.wso2.siddhi.core.SiddhiManager;
+import org.wso2.siddhi.core.event.Event;
+import org.wso2.siddhi.core.stream.input.InputHandler;
+import org.wso2.siddhi.core.stream.output.StreamCallback;
+import org.wso2.siddhi.core.util.EventPrinter;
+
+public class StringSubtractFunctionExtensionTest {
+private static final Logger LOG =
LoggerFactory.getLogger(StringSubtractFunctionExtensionTest.class);
+
+@Test
+public void testStringSubtract() throws Exception {
+String ql = " define stream log(timestamp long, switchLabel
string, port string, message string); " +
+" from log select string:subtract(\"a:b:c:d:e:f:g\",
\"g:a:e:d:z:r:s:c\") as alertKey insert into output; ";
+SiddhiManager manager = new SiddhiManager();
+ExecutionPlanRuntime runtime =
manager.createExecutionPlanRuntime(ql);
+runtime.addCallback("output", new StreamCallback() {
+@Override
+public void receive(Event[] events) {
+EventPrinter.print(events);
+Assert.assertTrue(events.length == 1);
+
Assert.assertTrue(events[0].getData(0).toString().equals("z\nr\ns"));
+}
+});
+
+runtime.start();
+
+InputHandler logInput = runtime.getInputHandler("log");
+
+Event e = new Event();
+e.setTimestamp(System.currentTimeMillis());
+e.setData(new Object[] {System.currentTimeMillis(),
"switch-ra-slc-01", "port01", "log-message"});
+logInput.send(e);
+
+Thread.sleep(1000);
--- End diff --
Avoid sleep in CEP ut
> add jmx resource info to Hadoop JMX Monitor
> ---
>
> Key: EAGLE-927
> URL: https://issues.apache.org/jira/browse/EAGLE-927
> Project: Eagle
> Issue Type: Improvement
> Components: App::Hadoop JMX Monitor
>Affects Versions: v0.5.0
>Reporter: wujinhu
>Assignee: wujinhu
> Fix For: v0.5.0
>
>
> We need add an stream(HADOOP_JMX_RESOURCE_STREAM) to stand for jmx resource
> like corrupt files and live nodes and so on. For example, when we found
> missing block number via HADOOP_JMX_METRIC_STREAM by define a policy, we can
> find missing block id via HADOOP_JMX_RESOURCE_STREAM
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] eagle pull request #839: [EAGLE-927] support for hadoop jmx resource info
Github user haoch commented on a diff in the pull request:
https://github.com/apache/eagle/pull/839#discussion_r102645205
--- Diff:
eagle-core/eagle-alert-parent/eagle-alert/alert-common/src/test/java/org/apache/eagle/siddhiext/StringSubtractFunctionExtensionTest.java
---
@@ -0,0 +1,62 @@
+/*
+ * 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.siddhiext;
+
+import org.junit.*;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+import org.wso2.siddhi.core.ExecutionPlanRuntime;
+import org.wso2.siddhi.core.SiddhiManager;
+import org.wso2.siddhi.core.event.Event;
+import org.wso2.siddhi.core.stream.input.InputHandler;
+import org.wso2.siddhi.core.stream.output.StreamCallback;
+import org.wso2.siddhi.core.util.EventPrinter;
+
+public class StringSubtractFunctionExtensionTest {
+private static final Logger LOG =
LoggerFactory.getLogger(StringSubtractFunctionExtensionTest.class);
+
+@Test
+public void testStringSubtract() throws Exception {
+String ql = " define stream log(timestamp long, switchLabel
string, port string, message string); " +
+" from log select string:subtract(\"a:b:c:d:e:f:g\",
\"g:a:e:d:z:r:s:c\") as alertKey insert into output; ";
+SiddhiManager manager = new SiddhiManager();
+ExecutionPlanRuntime runtime =
manager.createExecutionPlanRuntime(ql);
+runtime.addCallback("output", new StreamCallback() {
+@Override
+public void receive(Event[] events) {
+EventPrinter.print(events);
+Assert.assertTrue(events.length == 1);
+
Assert.assertTrue(events[0].getData(0).toString().equals("z\nr\ns"));
+}
+});
+
+runtime.start();
+
+InputHandler logInput = runtime.getInputHandler("log");
+
+Event e = new Event();
+e.setTimestamp(System.currentTimeMillis());
+e.setData(new Object[] {System.currentTimeMillis(),
"switch-ra-slc-01", "port01", "log-message"});
--- End diff --
Remove 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] [Commented] (EAGLE-927) add jmx resource info to Hadoop JMX Monitor
[ https://issues.apache.org/jira/browse/EAGLE-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879915#comment-15879915 ] ASF GitHub Bot commented on EAGLE-927: -- GitHub user wujinhu reopened a pull request: https://github.com/apache/eagle/pull/839 [EAGLE-927] support for hadoop jmx resource info You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/eagle EAGLE-927 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/839.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 #839 commit ddcd59616109caa7833af2d3e442cb9ad778ca28 Author: wujinhu Date: 2017-02-23T05:40:44Z support for hadoop jmx resource info > add jmx resource info to Hadoop JMX Monitor > --- > > Key: EAGLE-927 > URL: https://issues.apache.org/jira/browse/EAGLE-927 > Project: Eagle > Issue Type: Improvement > Components: App::Hadoop JMX Monitor >Affects Versions: v0.5.0 >Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > We need add an stream(HADOOP_JMX_RESOURCE_STREAM) to stand for jmx resource > like corrupt files and live nodes and so on. For example, when we found > missing block number via HADOOP_JMX_METRIC_STREAM by define a policy, we can > find missing block id via HADOOP_JMX_RESOURCE_STREAM -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #839: [EAGLE-927] support for hadoop jmx resource info
GitHub user wujinhu reopened a pull request: https://github.com/apache/eagle/pull/839 [EAGLE-927] support for hadoop jmx resource info You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/eagle EAGLE-927 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/839.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 #839 commit ddcd59616109caa7833af2d3e442cb9ad778ca28 Author: wujinhu Date: 2017-02-23T05:40:44Z support for hadoop jmx resource 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] [Commented] (EAGLE-927) add jmx resource info to Hadoop JMX Monitor
[ https://issues.apache.org/jira/browse/EAGLE-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879913#comment-15879913 ] ASF GitHub Bot commented on EAGLE-927: -- Github user wujinhu closed the pull request at: https://github.com/apache/eagle/pull/839 > add jmx resource info to Hadoop JMX Monitor > --- > > Key: EAGLE-927 > URL: https://issues.apache.org/jira/browse/EAGLE-927 > Project: Eagle > Issue Type: Improvement > Components: App::Hadoop JMX Monitor >Affects Versions: v0.5.0 >Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > We need add an stream(HADOOP_JMX_RESOURCE_STREAM) to stand for jmx resource > like corrupt files and live nodes and so on. For example, when we found > missing block number via HADOOP_JMX_METRIC_STREAM by define a policy, we can > find missing block id via HADOOP_JMX_RESOURCE_STREAM -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-927) add jmx resource info to Hadoop JMX Monitor
[ https://issues.apache.org/jira/browse/EAGLE-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879912#comment-15879912 ] ASF GitHub Bot commented on EAGLE-927: -- GitHub user wujinhu opened a pull request: https://github.com/apache/eagle/pull/839 [EAGLE-927] support for hadoop jmx resource info You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/eagle EAGLE-927 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/839.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 #839 commit ddcd59616109caa7833af2d3e442cb9ad778ca28 Author: wujinhu Date: 2017-02-23T05:40:44Z support for hadoop jmx resource info > add jmx resource info to Hadoop JMX Monitor > --- > > Key: EAGLE-927 > URL: https://issues.apache.org/jira/browse/EAGLE-927 > Project: Eagle > Issue Type: Improvement > Components: App::Hadoop JMX Monitor >Affects Versions: v0.5.0 >Reporter: wujinhu >Assignee: wujinhu > Fix For: v0.5.0 > > > We need add an stream(HADOOP_JMX_RESOURCE_STREAM) to stand for jmx resource > like corrupt files and live nodes and so on. For example, when we found > missing block number via HADOOP_JMX_METRIC_STREAM by define a policy, we can > find missing block id via HADOOP_JMX_RESOURCE_STREAM -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #839: [EAGLE-927] support for hadoop jmx resource info
Github user wujinhu closed the pull request at: https://github.com/apache/eagle/pull/839 --- 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] eagle pull request #839: [EAGLE-927] support for hadoop jmx resource info
GitHub user wujinhu opened a pull request: https://github.com/apache/eagle/pull/839 [EAGLE-927] support for hadoop jmx resource info You can merge this pull request into a Git repository by running: $ git pull https://github.com/wujinhu/eagle EAGLE-927 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/839.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 #839 commit ddcd59616109caa7833af2d3e442cb9ad778ca28 Author: wujinhu Date: 2017-02-23T05:40:44Z support for hadoop jmx resource 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] [Assigned] (EAGLE-924) urls to healthy and unhealthy region-servers in hbase dashboard is not accurate enough
[ https://issues.apache.org/jira/browse/EAGLE-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiJun Tang reassigned EAGLE-924: Assignee: Lingang Deng (was: JiJun Tang) > urls to healthy and unhealthy region-servers in hbase dashboard is not > accurate enough > -- > > Key: EAGLE-924 > URL: https://issues.apache.org/jira/browse/EAGLE-924 > Project: Eagle > Issue Type: Bug > Components: App::Hadoop JMX Monitor >Affects Versions: v0.5.0 >Reporter: Michael Wu >Assignee: Lingang Deng > Fix For: v0.6.0 > > Attachments: Screen Shot 2017-02-22 at 16.24.09.png > > > Issue: In hbase dashboard of a site, in the top section, there are 2 links > referring to urls of healthy and unhealthy region-server lists. But > currently, when people click the link, the page is directed to a full list of > all region-servers, not the corresponding healthy-list or unhealthy-list. > Suggestion: we can add some filter in the url, for example, append > "?status=healthy" or "?status=unhealthy" to the url, and update the link with > new urls. > Please see the screenshot in the attachment of this ticket. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #838: [MINOR] Add kafka log4j appender integration test cases
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/838 @DadanielZ merged, please pull latest code for testing. --- 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] eagle pull request #838: [MINOR] Add kafka log4j appender integration test c...
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/838 --- 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-927) add jmx resource info to Hadoop JMX Monitor
wujinhu created EAGLE-927: - Summary: add jmx resource info to Hadoop JMX Monitor Key: EAGLE-927 URL: https://issues.apache.org/jira/browse/EAGLE-927 Project: Eagle Issue Type: Improvement Components: App::Hadoop JMX Monitor Affects Versions: v0.5.0 Reporter: wujinhu Assignee: wujinhu Fix For: v0.5.0 We need add an stream(HADOOP_JMX_RESOURCE_STREAM) to stand for jmx resource like corrupt files and live nodes and so on. For example, when we found missing block number via HADOOP_JMX_METRIC_STREAM by define a policy, we can find missing block id via HADOOP_JMX_RESOURCE_STREAM -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (EAGLE-926) Alert engine fails to support more than one stream consumption from an application
Zhao, Qingwen created EAGLE-926: --- Summary: Alert engine fails to support more than one stream consumption from an application Key: EAGLE-926 URL: https://issues.apache.org/jira/browse/EAGLE-926 Project: Eagle Issue Type: Bug Affects Versions: v0.5.0 Reporter: Zhao, Qingwen Assignee: Zhao, Qingwen 1. refactor StreamDefinition and rename 'dataSource' -> 'sourceStream' 2. refactor Kafka2TupleMetadata and define name as streamName instead of appId and store appId value in a new field 'appId' -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #838: [MINOR] Add kafka log4j appender integration test cases
Github user DadanielZ commented on the issue: https://github.com/apache/eagle/pull/838 @haoch thank you Hao, will test 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-888) Application submitted to Storm is always shown as “HBaseAuditLogApp”
[
https://issues.apache.org/jira/browse/EAGLE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
DanielZhou closed EAGLE-888.
Resolution: Fixed
This only happens in dev env: when starting eagle server from class
"ServerMain", due to multiple "application.conf" exist in.
The correct way to debug is to use "ServerDebug" class to start eagle server.
Issues resolved, hence closing it
> Application submitted to Storm is always shown as “HBaseAuditLogApp”
> -
>
> Key: EAGLE-888
> URL: https://issues.apache.org/jira/browse/EAGLE-888
> Project: Eagle
> Issue Type: Bug
> Components: Core::App Engine
>Affects Versions: v0.5.0
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> *Issue*:
> Steps to reproduce:
> - Started application from Eagle UI (eg: alert engine)
> - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
> *Reason*:
> In the constructor function of class *"ApplicationAction"*:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
> .withFallback(serverConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> {quote}
> According to the java doc of
> [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
> :
> {quote}
> Returns a new value computed by merging this value with another, with keys in
> this value "winning" over the other one.
> {quote}
> As a result, "serverConfig" will win over
> "ConfigFactory.parseMap(metadata.getContext())" which means the default
> "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
> will win over the meta data of the user's topology.
> *Fix*:
> Change the order of "withFallBack" to:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> .withFallback(serverConfig)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] eagle issue #796: [EAGLE-888] Application submitted to Storm is always shown...
Github user DadanielZ commented on the issue: https://github.com/apache/eagle/pull/796 Issues resolved, hence closing 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-888) Application submitted to Storm is always shown as “HBaseAuditLogApp”
[
https://issues.apache.org/jira/browse/EAGLE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878877#comment-15878877
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user DadanielZ commented on the issue:
https://github.com/apache/eagle/pull/796
Issues resolved, hence closing it.
> Application submitted to Storm is always shown as “HBaseAuditLogApp”
> -
>
> Key: EAGLE-888
> URL: https://issues.apache.org/jira/browse/EAGLE-888
> Project: Eagle
> Issue Type: Bug
> Components: Core::App Engine
>Affects Versions: v0.5.0
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> *Issue*:
> Steps to reproduce:
> - Started application from Eagle UI (eg: alert engine)
> - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
> *Reason*:
> In the constructor function of class *"ApplicationAction"*:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
> .withFallback(serverConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> {quote}
> According to the java doc of
> [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
> :
> {quote}
> Returns a new value computed by merging this value with another, with keys in
> this value "winning" over the other one.
> {quote}
> As a result, "serverConfig" will win over
> "ConfigFactory.parseMap(metadata.getContext())" which means the default
> "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
> will win over the meta data of the user's topology.
> *Fix*:
> Change the order of "withFallBack" to:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> .withFallback(serverConfig)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (EAGLE-888) Application submitted to Storm is always shown as “HBaseAuditLogApp”
[
https://issues.apache.org/jira/browse/EAGLE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878878#comment-15878878
]
ASF GitHub Bot commented on EAGLE-888:
--
Github user DadanielZ closed the pull request at:
https://github.com/apache/eagle/pull/796
> Application submitted to Storm is always shown as “HBaseAuditLogApp”
> -
>
> Key: EAGLE-888
> URL: https://issues.apache.org/jira/browse/EAGLE-888
> Project: Eagle
> Issue Type: Bug
> Components: Core::App Engine
>Affects Versions: v0.5.0
>Reporter: DanielZhou
>Assignee: DanielZhou
>
> *Issue*:
> Steps to reproduce:
> - Started application from Eagle UI (eg: alert engine)
> - Go to Storm UI, topology name is shown as *"HBaseAuditLogApp"*
> *Reason*:
> In the constructor function of class *"ApplicationAction"*:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
> .withFallback(serverConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> {quote}
> According to the java doc of
> [withFallBack(theOther)|http://typesafehub.github.io/config/latest/api/com/typesafe/config/Config.html#withFallback-com.typesafe.config.ConfigMergeable-]
> :
> {quote}
> Returns a new value computed by merging this value with another, with keys in
> this value "winning" over the other one.
> {quote}
> As a result, "serverConfig" will win over
> "ConfigFactory.parseMap(metadata.getContext())" which means the default
> "ConfigString(appId="HBaseAuditApp")" and "ConfigString(siteId="testSite")"
> will win over the meta data of the user's topology.
> *Fix*:
> Change the order of "withFallBack" to:
> {quote}
> this.effectiveConfig = ConfigFactory.parseMap(executionConfig)
>
> .withFallback(ConfigFactory.parseMap(metadata.getContext()))
> .withFallback(serverConfig)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] eagle pull request #796: [EAGLE-888] Application submitted to Storm is alway...
Github user DadanielZ closed the pull request at: https://github.com/apache/eagle/pull/796 --- 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] eagle issue #838: [MINOR] Add kafka log4j appender integration test cases
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/838 @DadanielZ please check the PR about `KafkaLog4jAppenderIT ` for debug once build passed. --- 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] eagle pull request #838: [MINOR] Add kafka log4j appender integration test c...
GitHub user haoch opened a pull request: https://github.com/apache/eagle/pull/838 [MINOR] Add kafka log4j appender integration test cases * Add kafka log4j appender integration test cases `KafkaLog4jAppenderIT` You can merge this pull request into a Git repository by running: $ git pull https://github.com/haoch/eagle AddKafkaLog4jAppenderIT Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/838.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 #838 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Resolved] (EAGLE-908) Hdfs JMX Monitoring Dashboard
[ https://issues.apache.org/jira/browse/EAGLE-908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen resolved EAGLE-908. Resolution: Fixed > Hdfs JMX Monitoring Dashboard > - > > Key: EAGLE-908 > URL: https://issues.apache.org/jira/browse/EAGLE-908 > Project: Eagle > Issue Type: New Feature > Components: App::Hadoop JMX Monitor, Core::UI Engine >Reporter: Lingang Deng >Assignee: JiJun Tang > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #837: [MINOR] Support source_host aside host in metric co...
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/837 --- 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] eagle pull request #837: [MINOR] Support source_host aside host in metric co...
GitHub user haoch opened a pull request: https://github.com/apache/eagle/pull/837 [MINOR] Support source_host aside host in metric collector Support source_host aside host in metric collector for case when requesting host is not the actual host for reason like network settings. You can merge this pull request into a Git repository by running: $ git pull https://github.com/haoch/eagle patch-3 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/837.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 #837 commit 7a52ce7e59570da58d60947770becbf6081b7243 Author: Hao Chen Date: 2017-02-22T13:57:11Z [MINOR] Support source_host aside host in metric collector --- 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-908) Hdfs JMX Monitoring Dashboard
[ https://issues.apache.org/jira/browse/EAGLE-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878140#comment-15878140 ] ASF GitHub Bot commented on EAGLE-908: -- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/836 > Hdfs JMX Monitoring Dashboard > - > > Key: EAGLE-908 > URL: https://issues.apache.org/jira/browse/EAGLE-908 > Project: Eagle > Issue Type: New Feature > Components: App::Hadoop JMX Monitor, Core::UI Engine >Reporter: Lingang Deng >Assignee: JiJun Tang > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #836: [EAGLE-908] Hdfs JMX Monitoring Dashboard
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/836 --- 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-908) Hdfs JMX Monitoring Dashboard
[ https://issues.apache.org/jira/browse/EAGLE-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878138#comment-15878138 ] ASF GitHub Bot commented on EAGLE-908: -- Github user haoch commented on the issue: https://github.com/apache/eagle/pull/836 Build is related to unstable unit test case `MapRFSAuditLogAppProviderTest`. > Hdfs JMX Monitoring Dashboard > - > > Key: EAGLE-908 > URL: https://issues.apache.org/jira/browse/EAGLE-908 > Project: Eagle > Issue Type: New Feature > Components: App::Hadoop JMX Monitor, Core::UI Engine >Reporter: Lingang Deng >Assignee: JiJun Tang > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #836: [EAGLE-908] Hdfs JMX Monitoring Dashboard
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/836 Build is related to unstable unit test case `MapRFSAuditLogAppProviderTest`. --- 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-908) Hdfs JMX Monitoring Dashboard
[ https://issues.apache.org/jira/browse/EAGLE-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878132#comment-15878132 ] ASF GitHub Bot commented on EAGLE-908: -- Github user haoch commented on the issue: https://github.com/apache/eagle/pull/836 Is this feature finished? > Hdfs JMX Monitoring Dashboard > - > > Key: EAGLE-908 > URL: https://issues.apache.org/jira/browse/EAGLE-908 > Project: Eagle > Issue Type: New Feature > Components: App::Hadoop JMX Monitor, Core::UI Engine >Reporter: Lingang Deng >Assignee: JiJun Tang > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #836: [EAGLE-908] Hdfs JMX Monitoring Dashboard
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/836 Is this feature finished? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Assigned] (EAGLE-925) Eagle Docker Image for v0.5
[ https://issues.apache.org/jira/browse/EAGLE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen reassigned EAGLE-925: -- Assignee: Jayesh (was: Hao Chen) > Eagle Docker Image for v0.5 > --- > > Key: EAGLE-925 > URL: https://issues.apache.org/jira/browse/EAGLE-925 > Project: Eagle > Issue Type: New Feature > Components: Integration::Docker >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Jayesh > Fix For: v0.5.0 > > > As we do a lot of refactor for v0.5 so we need to create a new Eagle Docker > for v0.5, referring to > https://github.com/apache/eagle/tree/branch-0.4/eagle-external/eagle-docker > which is out of date. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (EAGLE-925) Eagle Docker Image for v0.5
[ https://issues.apache.org/jira/browse/EAGLE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-925: --- Description: As we do a lot of refactor for v0.5 so we need to create a new Eagle Docker for v0.5, referring to https://github.com/apache/eagle/tree/branch-0.4/eagle-external/eagle-docker which is out of date. (was: As we do a lot of refactor for v0.5 so we need to create a new Eagle Docker for v0.5, referring to https://github.com/apache/eagle/tree/branch-0.4/eagle-external/eagle-docker which is out of date. Older reference: https://github.com/apache/eagle/tree/branch-0.4/eagle-external/eagle-docker) > Eagle Docker Image for v0.5 > --- > > Key: EAGLE-925 > URL: https://issues.apache.org/jira/browse/EAGLE-925 > Project: Eagle > Issue Type: New Feature > Components: Integration::Docker >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > As we do a lot of refactor for v0.5 so we need to create a new Eagle Docker > for v0.5, referring to > https://github.com/apache/eagle/tree/branch-0.4/eagle-external/eagle-docker > which is out of date. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-908) Hdfs JMX Monitoring Dashboard
[ https://issues.apache.org/jira/browse/EAGLE-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877967#comment-15877967 ] ASF GitHub Bot commented on EAGLE-908: -- GitHub user chitin opened a pull request: https://github.com/apache/eagle/pull/836 [EAGLE-908] Hdfs JMX Monitoring Dashboard [EAGLE-908] Hdfs JMX Monitoring Dashboard - Hdfs overview page, use tab to show multiple active namenode, hdfs summary is displayed at the upper portion of the page. https://issues.apache.org/jira/browse/EAGLE-908 You can merge this pull request into a Git repository by running: $ git pull https://github.com/chitin/eagle eagle908-2 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/836.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 #836 commit a263395580bd68f32b5dfe4006864787ab2ceab7 Author: chitin Date: 2017-02-22T10:33:50Z [EAGLE-908] Hdfs JMX Monitoring Dashboard - Hdfs overview page, use tab to show multiple active namenode, hdfs summary is displayed at the upper portion of the page. https://issues.apache.org/jira/browse/EAGLE-908 > Hdfs JMX Monitoring Dashboard > - > > Key: EAGLE-908 > URL: https://issues.apache.org/jira/browse/EAGLE-908 > Project: Eagle > Issue Type: New Feature > Components: App::Hadoop JMX Monitor, Core::UI Engine >Reporter: Lingang Deng >Assignee: JiJun Tang > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #836: [EAGLE-908] Hdfs JMX Monitoring Dashboard
GitHub user chitin opened a pull request: https://github.com/apache/eagle/pull/836 [EAGLE-908] Hdfs JMX Monitoring Dashboard [EAGLE-908] Hdfs JMX Monitoring Dashboard - Hdfs overview page, use tab to show multiple active namenode, hdfs summary is displayed at the upper portion of the page. https://issues.apache.org/jira/browse/EAGLE-908 You can merge this pull request into a Git repository by running: $ git pull https://github.com/chitin/eagle eagle908-2 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/836.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 #836 commit a263395580bd68f32b5dfe4006864787ab2ceab7 Author: chitin Date: 2017-02-22T10:33:50Z [EAGLE-908] Hdfs JMX Monitoring Dashboard - Hdfs overview page, use tab to show multiple active namenode, hdfs summary is displayed at the upper portion of the page. https://issues.apache.org/jira/browse/EAGLE-908 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (EAGLE-925) Eagle Docker Image for v0.5
[ https://issues.apache.org/jira/browse/EAGLE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-925: --- Description: As we do a lot of refactor for v0.5 so we need to create a new Eagle Docker for v0.5, referring to https://github.com/apache/eagle/tree/branch-0.4/eagle-external/eagle-docker which is out of date. Older reference: https://github.com/apache/eagle/tree/branch-0.4/eagle-external/eagle-docker was:As we do a lot of refactor for v0.5 so we need to create a new Eagle Docker for v0.5, referring to https://github.com/apache/eagle/tree/branch-0.4/eagle-external/eagle-docker which is out of date. > Eagle Docker Image for v0.5 > --- > > Key: EAGLE-925 > URL: https://issues.apache.org/jira/browse/EAGLE-925 > Project: Eagle > Issue Type: New Feature > Components: Integration::Docker >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > As we do a lot of refactor for v0.5 so we need to create a new Eagle Docker > for v0.5, referring to > https://github.com/apache/eagle/tree/branch-0.4/eagle-external/eagle-docker > which is out of date. > Older reference: > https://github.com/apache/eagle/tree/branch-0.4/eagle-external/eagle-docker -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (EAGLE-925) Eagle Docker Image for v0.5
Hao Chen created EAGLE-925: -- Summary: Eagle Docker Image for v0.5 Key: EAGLE-925 URL: https://issues.apache.org/jira/browse/EAGLE-925 Project: Eagle Issue Type: New Feature Affects Versions: v0.5.0 Reporter: Hao Chen Assignee: Hao Chen Fix For: v0.5.0 As we do a lot of refactor for v0.5 so we need to create a new Eagle Docker for v0.5, referring to https://github.com/apache/eagle/tree/branch-0.4/eagle-external/eagle-docker which is out of date. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (EAGLE-925) Eagle Docker Image for v0.5
[ https://issues.apache.org/jira/browse/EAGLE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Chen updated EAGLE-925: --- Component/s: Integration::Docker > Eagle Docker Image for v0.5 > --- > > Key: EAGLE-925 > URL: https://issues.apache.org/jira/browse/EAGLE-925 > Project: Eagle > Issue Type: New Feature > Components: Integration::Docker >Affects Versions: v0.5.0 >Reporter: Hao Chen >Assignee: Hao Chen > Fix For: v0.5.0 > > > As we do a lot of refactor for v0.5 so we need to create a new Eagle Docker > for v0.5, referring to > https://github.com/apache/eagle/tree/branch-0.4/eagle-external/eagle-docker > which is out of date. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (EAGLE-906) update required storm packages to 1.x
[ https://issues.apache.org/jira/browse/EAGLE-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877902#comment-15877902 ] ASF GitHub Bot commented on EAGLE-906: -- Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/812 ok, I m digging further into this, I will try running some apps. pls let me know if you have any other suggestions. > update required storm packages to 1.x > - > > Key: EAGLE-906 > URL: https://issues.apache.org/jira/browse/EAGLE-906 > Project: Eagle > Issue Type: Sub-task >Reporter: Jayesh >Assignee: Jayesh > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #812: [EAGLE-906] org.apache.storm 1.x with API changes
Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/812 ok, I m digging further into this, I will try running some apps. pls let me know if you have any other suggestions. --- 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-906) update required storm packages to 1.x
[ https://issues.apache.org/jira/browse/EAGLE-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877866#comment-15877866 ] ASF GitHub Bot commented on EAGLE-906: -- Github user haoch commented on the issue: https://github.com/apache/eagle/pull/812 Just worry about potential compatibility issue as `kafka` which was refactored a lot recently and here are some tricky dependencies behavior in `storm-kafka` > update required storm packages to 1.x > - > > Key: EAGLE-906 > URL: https://issues.apache.org/jira/browse/EAGLE-906 > Project: Eagle > Issue Type: Sub-task >Reporter: Jayesh >Assignee: Jayesh > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle issue #812: [EAGLE-906] org.apache.storm 1.x with API changes
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/812 Just worry about potential compatibility issue as `kafka` which was refactored a lot recently and here are some tricky dependencies behavior in `storm-kafka` --- 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] eagle pull request #835: [MINOR] fix jslint check
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/835 --- 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] eagle pull request #835: [MINOR] fix jslint check
GitHub user zombieJ opened a pull request: https://github.com/apache/eagle/pull/835 [MINOR] fix jslint check Update js alertCtrl to fit with jslint You can merge this pull request into a Git repository by running: $ git pull https://github.com/zombieJ/incubator-eagle jslintFix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/eagle/pull/835.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 #835 commit 324c256c88f04d8670194fe4c0b8b4b1c7292161 Author: zombieJ Date: 2017-02-22T09:14:18Z fix jslint --- 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-919) Fix mr history null pointer exception when counters are null
[ https://issues.apache.org/jira/browse/EAGLE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877786#comment-15877786 ] ASF GitHub Bot commented on EAGLE-919: -- Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/833 > Fix mr history null pointer exception when counters are null > > > Key: EAGLE-919 > URL: https://issues.apache.org/jira/browse/EAGLE-919 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Zhao, Qingwen >Assignee: Zhao, Qingwen > > Fix null pointer exception in mr history job parser when counters are null -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] eagle pull request #833: EAGLE-919: Fix null pointer exception in JobSuggest...
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/833 --- 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-924) urls to healthy and unhealthy region-servers in hbase dashboard is not accurate enough
Michael Wu created EAGLE-924: Summary: urls to healthy and unhealthy region-servers in hbase dashboard is not accurate enough Key: EAGLE-924 URL: https://issues.apache.org/jira/browse/EAGLE-924 Project: Eagle Issue Type: Bug Components: App::Hadoop JMX Monitor Affects Versions: v0.5.0 Reporter: Michael Wu Assignee: JiJun Tang Fix For: v0.6.0 Attachments: Screen Shot 2017-02-22 at 16.24.09.png Issue: In hbase dashboard of a site, in the top section, there are 2 links referring to urls of healthy and unhealthy region-server lists. But currently, when people click the link, the page is directed to a full list of all region-servers, not the corresponding healthy-list or unhealthy-list. Suggestion: we can add some filter in the url, for example, append "?status=healthy" or "?status=unhealthy" to the url, and update the link with new urls. Please see the screenshot in the attachment of this ticket. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (EAGLE-918) Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth
[
https://issues.apache.org/jira/browse/EAGLE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen resolved EAGLE-918.
Resolution: Fixed
> Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth
>
>
> Key: EAGLE-918
> URL: https://issues.apache.org/jira/browse/EAGLE-918
> Project: Eagle
> Issue Type: New Feature
> Components: Core::Eagle Server
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> * Improve eagle auth framework to support annotations under Jersey 1.9 and
> Dropwizard 0.7.1
> {code}
> @PermitAll
> @DenyAll
> @RolesAllowed
> @Auth
> {code}
> * Add Authentication API
> {code}
> GET /auth/principal
> GET /auth/validate
> GET /auth/login
> {code}
> * Add password encryption and EncrytTool
> {code}
> java ServerMain encrypt [text to encrypt]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (EAGLE-918) Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth
[
https://issues.apache.org/jira/browse/EAGLE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877743#comment-15877743
]
ASF GitHub Bot commented on EAGLE-918:
--
Github user asfgit closed the pull request at:
https://github.com/apache/eagle/pull/831
> Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth
>
>
> Key: EAGLE-918
> URL: https://issues.apache.org/jira/browse/EAGLE-918
> Project: Eagle
> Issue Type: New Feature
> Components: Core::Eagle Server
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> * Improve eagle auth framework to support annotations under Jersey 1.9 and
> Dropwizard 0.7.1
> {code}
> @PermitAll
> @DenyAll
> @RolesAllowed
> @Auth
> {code}
> * Add Authentication API
> {code}
> GET /auth/principal
> GET /auth/validate
> GET /auth/login
> {code}
> * Add password encryption and EncrytTool
> {code}
> java ServerMain encrypt [text to encrypt]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] eagle pull request #831: [EAGLE-918] Support auth annotations PermitAll/Deny...
Github user asfgit closed the pull request at: https://github.com/apache/eagle/pull/831 --- 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-918) Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth
[
https://issues.apache.org/jira/browse/EAGLE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877739#comment-15877739
]
ASF GitHub Bot commented on EAGLE-918:
--
Github user haoch commented on the issue:
https://github.com/apache/eagle/pull/831
Merged as Approved by @r7raul1984
> Improve eagle auth framework to support @PermitAll/DenyAll/RolesAllowed/Auth
>
>
> Key: EAGLE-918
> URL: https://issues.apache.org/jira/browse/EAGLE-918
> Project: Eagle
> Issue Type: New Feature
> Components: Core::Eagle Server
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> * Improve eagle auth framework to support annotations under Jersey 1.9 and
> Dropwizard 0.7.1
> {code}
> @PermitAll
> @DenyAll
> @RolesAllowed
> @Auth
> {code}
> * Add Authentication API
> {code}
> GET /auth/principal
> GET /auth/validate
> GET /auth/login
> {code}
> * Add password encryption and EncrytTool
> {code}
> java ServerMain encrypt [text to encrypt]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] eagle issue #831: [EAGLE-918] Support auth annotations PermitAll/DenyAll/Rol...
Github user haoch commented on the issue: https://github.com/apache/eagle/pull/831 Merged as Approved by @r7raul1984 --- 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. ---
