[jira] [Updated] (EAGLE-222) Documentation for eagle alert plugin mechnism

2016-04-22 Thread Zhao, Qingwen (JIRA)

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

Zhao, Qingwen updated EAGLE-222:

Assignee: Zhao, Qingwen  (was: Senthilkumar)

> Documentation for eagle alert plugin mechnism
> -
>
> Key: EAGLE-222
> URL: https://issues.apache.org/jira/browse/EAGLE-222
> Project: Eagle
>  Issue Type: Task
>Affects Versions: v0.3.0
>Reporter: Su Ralph
>Assignee: Zhao, Qingwen
> Fix For: v0.4.0
>
>
> Eagle alert plugin is supported in backend. EAGLE-221 will support in user 
> interface side. This JIRA to provide end-user documentation including:
> 1. How to create policy with different alert notification type.
> 2. How to write an customized notification
> 3. How notification plugin would be called during data flow.



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


[jira] [Commented] (EAGLE-274) 2016-04-15 15:50:20 b.s.d.worker [ERROR] Error on initialization of server mk-worker java.lang.RuntimeException: java.lang.ClassNotFoundException: org.slf4j.impl.Log4jLo

2016-04-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on EAGLE-274:
--

Github user qingwen220 commented on the pull request:

https://github.com/apache/incubator-eagle/pull/161#issuecomment-213363441
  
This exception will occur if we storm topology by 
bin/kafka-stream-monitor.sh, as the classpath contains slf4j-log4j12-*.jar


> 2016-04-15 15:50:20 b.s.d.worker [ERROR] Error on initialization of server 
> mk-worker java.lang.RuntimeException: java.lang.ClassNotFoundException: 
> org.slf4j.impl.Log4jLoggerAdapter
> 
>
> Key: EAGLE-274
> URL: https://issues.apache.org/jira/browse/EAGLE-274
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Zhao, Qingwen
> Fix For: v0.4.0
>
>
> 2016-04-15 15:50:20 b.s.d.worker [ERROR] Error on initialization of server 
> mk-worker java.lang.RuntimeException: java.lang.ClassNotFoundException: 
> org.slf4j.impl.Log4jLoggerAdapter



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


[GitHub] incubator-eagle pull request: EAGLE-274 Fix java.lang.ClassNotFoun...

2016-04-22 Thread qingwen220
Github user qingwen220 commented on the pull request:

https://github.com/apache/incubator-eagle/pull/161#issuecomment-213363441
  
This exception will occur if we storm topology by 
bin/kafka-stream-monitor.sh, as the classpath contains slf4j-log4j12-*.jar


---
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: EAGLE-274 Fix java.lang.ClassNotFoun...

2016-04-22 Thread qingwen220
GitHub user qingwen220 opened a pull request:

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

EAGLE-274 Fix java.lang.ClassNotFoundException: 
org.slf4j.impl.Log4jLoggerAdapter

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

slf4j-log4j12-*.jar under lib/share conflicts with Storm jars

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

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

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

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


commit 99b25759c0f742bea27a60773808bf5b8ceffc3d
Author: Zhao, Qingwen 
Date:   2016-04-22T09:48:37Z

Fix java.lang.ClassNotFoundException: org.slf4j.impl.Log4jLoggerAdapter




---
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-274) 2016-04-15 15:50:20 b.s.d.worker [ERROR] Error on initialization of server mk-worker java.lang.RuntimeException: java.lang.ClassNotFoundException: org.slf4j.impl.Log4jLo

2016-04-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on EAGLE-274:
--

GitHub user qingwen220 opened a pull request:

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

EAGLE-274 Fix java.lang.ClassNotFoundException: 
org.slf4j.impl.Log4jLoggerAdapter

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

slf4j-log4j12-*.jar under lib/share conflicts with Storm jars

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

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

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

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


commit 99b25759c0f742bea27a60773808bf5b8ceffc3d
Author: Zhao, Qingwen 
Date:   2016-04-22T09:48:37Z

Fix java.lang.ClassNotFoundException: org.slf4j.impl.Log4jLoggerAdapter




> 2016-04-15 15:50:20 b.s.d.worker [ERROR] Error on initialization of server 
> mk-worker java.lang.RuntimeException: java.lang.ClassNotFoundException: 
> org.slf4j.impl.Log4jLoggerAdapter
> 
>
> Key: EAGLE-274
> URL: https://issues.apache.org/jira/browse/EAGLE-274
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.3.0
>Reporter: Hao Chen
>Assignee: Zhao, Qingwen
> Fix For: v0.4.0
>
>
> 2016-04-15 15:50:20 b.s.d.worker [ERROR] Error on initialization of server 
> mk-worker java.lang.RuntimeException: java.lang.ClassNotFoundException: 
> org.slf4j.impl.Log4jLoggerAdapter



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


[jira] [Commented] (EAGLE-271) Topology management in remote mode including start/stop/status operations

2016-04-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on EAGLE-271:
--

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

https://github.com/apache/incubator-eagle/pull/160#discussion_r60705328
  
--- Diff: eagle-assembly/src/main/conf/eagle-scheduler.conf ---
@@ -0,0 +1,41 @@
+# 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.
+
+
+### scheduler propertise
+appCommandLoaderInterval = 1
+appHealthCheckInterval = 5
--- End diff --

Good suggestion. I will update it. 


> Topology management in remote mode including start/stop/status operations
> -
>
> Key: EAGLE-271
> URL: https://issues.apache.org/jira/browse/EAGLE-271
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.4.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>




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


[GitHub] incubator-eagle pull request: EAGLE-271 Topology management in rem...

2016-04-22 Thread qingwen220
Github user qingwen220 commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/160#discussion_r60705328
  
--- Diff: eagle-assembly/src/main/conf/eagle-scheduler.conf ---
@@ -0,0 +1,41 @@
+# 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.
+
+
+### scheduler propertise
+appCommandLoaderInterval = 1
+appHealthCheckInterval = 5
--- End diff --

Good suggestion. I will update 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-271) Topology management in remote mode including start/stop/status operations

2016-04-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on EAGLE-271:
--

Github user RalphSu commented on the pull request:

https://github.com/apache/incubator-eagle/pull/160#issuecomment-213301484
  
Big PR. it's good to me unless the config item name.
+1


> Topology management in remote mode including start/stop/status operations
> -
>
> Key: EAGLE-271
> URL: https://issues.apache.org/jira/browse/EAGLE-271
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.4.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>




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


[GitHub] incubator-eagle pull request: EAGLE-271 Topology management in rem...

2016-04-22 Thread RalphSu
Github user RalphSu commented on the pull request:

https://github.com/apache/incubator-eagle/pull/160#issuecomment-213301484
  
Big PR. it's good to me unless the config item name.
+1


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


[jira] [Commented] (EAGLE-271) Topology management in remote mode including start/stop/status operations

2016-04-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on EAGLE-271:
--

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

https://github.com/apache/incubator-eagle/pull/160#discussion_r60699439
  
--- Diff: eagle-assembly/src/main/conf/eagle-scheduler.conf ---
@@ -0,0 +1,41 @@
+# 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.
+
+
+### scheduler propertise
+appCommandLoaderInterval = 1
+appHealthCheckInterval = 5
--- End diff --

Better to have unit in name of config when relate to time.


> Topology management in remote mode including start/stop/status operations
> -
>
> Key: EAGLE-271
> URL: https://issues.apache.org/jira/browse/EAGLE-271
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.4.0
>Reporter: Zhao, Qingwen
>Assignee: Zhao, Qingwen
>




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


[GitHub] incubator-eagle pull request: EAGLE-271 Topology management in rem...

2016-04-22 Thread RalphSu
Github user RalphSu commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/160#discussion_r60699439
  
--- Diff: eagle-assembly/src/main/conf/eagle-scheduler.conf ---
@@ -0,0 +1,41 @@
+# 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.
+
+
+### scheduler propertise
+appCommandLoaderInterval = 1
+appHealthCheckInterval = 5
--- End diff --

Better to have unit in name of config when relate to time.


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