from:"Karol Brejna"

Re: [VOTE] Retire Gearpump

2018-09-13 Thread Karol Brejna

+1

W dniu czw., 13.09.2018 o 07:54 Manu Zhang 
napisał(a):

> Hi all,
>
> As per previous discussion
> <
> https://lists.apache.org/thread.html/77946cfff4557cf10c13c2d35fc165223583e58c2f7705319acabcf4@%3Cdev.gearpump.apache.org%3E
> >,
> we agree that it would be better for Gearpump to retire from the ASF
> incubator. Here comes the formal vote.
>
> [ ] +1 to retire
> [ ] -1 not to retire because...
>
> Here's my +1.
>
> This will be open for at least 72 hours and is a majority vote.
>
> Thanks,
> Manu Zhang
>

Re: [DISCUSS] Retire Gearpump

2018-09-12 Thread Karol Brejna

Manu,

Thanks for bringing this difficult topic.

I was struggling with it myself.

Here are my thoughts:

Our main objectives were to build the community and gain more adoption.

Although there was some considerable interest, I think we were not able to
build a stable and sizable community around our project.

We have identified some "technical" goals to achieve as the next steps.
Without a broader community, I think we won't be able to keep a decent
development activity and release pace.

It doesn't look that the situation (community) would change any time soon,
so - with a heavy heart - I must agree that it would be only fair to the
Apache community to retire Gearpump.

I am hoping we'll continue working on Gearpump in some other "formula" in
the future, as it has some strengths and is cool to use and develop ;-)

Regards,
Karol

On Sun, Sep 9, 2018 at 9:38 AM Manu Zhang  wrote:

> Hi all,
>
> Gearpump has been an Apache incubator since 2016-03-08. Thank you all for
> help to  incubate Gearpump and keep it move forward.
>
> The activity around Gearpump has, however, slowed down and the last release
> was more than one year ago. There is no sign of a growing community, which
> is a requirement to be a Apache TLP. The long period of release process has
> made things even harder for such a slim community.
>
> I don't see a future for Gearpump within Apache so it's better off to
> leave.
>
> What do you think ?
>
> Thanks,
> Manu Zhang
>

[jira] [Updated] (GEARPUMP-378) http://gearpump.apache.org/license.html: "full license statement" doesn't work

2018-05-08 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-378:
--
Description: "Here is the [full license 
statement|http://gearpump.apache.org/LICENSE] for all its dependencies." leads 
to http://gearpump.apache.org/LICENSE which doesn't exist.  (was: APACHE 
PROJECT WEBSITE BRANDING POLICY
notes (among others) that "License" should link to: 
http://www.apache.org/licenses/.

We link to http://gearpump.apache.org/license.html (from apache.gearpump.org).

Review other requirements and verify if we meet them.)

> http://gearpump.apache.org/license.html: "full license statement" doesn't work
> --
>
> Key: GEARPUMP-378
> URL: https://issues.apache.org/jira/browse/GEARPUMP-378
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: doc
>Affects Versions: 0.8.4
>        Reporter: Karol Brejna
>Assignee: Karol Brejna
>Priority: Trivial
>
> "Here is the [full license statement|http://gearpump.apache.org/LICENSE] for 
> all its dependencies." leads to http://gearpump.apache.org/LICENSE which 
> doesn't exist.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEARPUMP-378) http://gearpump.apache.org/license.html: "full license statement" doesn't work

2018-05-08 Thread Karol Brejna (JIRA)

Karol Brejna created GEARPUMP-378:
-

 Summary: http://gearpump.apache.org/license.html: "full license 
statement" doesn't work
 Key: GEARPUMP-378
 URL: https://issues.apache.org/jira/browse/GEARPUMP-378
 Project: Apache Gearpump
  Issue Type: Bug
  Components: doc
Affects Versions: 0.8.4
Reporter: Karol Brejna
Assignee: Karol Brejna


APACHE PROJECT WEBSITE BRANDING POLICY
notes (among others) that "License" should link to: 
http://www.apache.org/licenses/.

We link to http://gearpump.apache.org/license.html (from apache.gearpump.org).

Review other requirements and verify if we meet them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] incubator-gearpump issue #241: [WiP][GEARPUMP-368] Restore setting runtime e...

2018-04-27 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/241
  
Some IT tests failing. Trying to investigate.


---

[GitHub] incubator-gearpump issue #241: [WiP][GEARPUMP-368] Restore setting runtime e...

2018-04-23 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/241
  
I did search for AkkaApp usages and there are few groups of them:
1. examples (proper AkkaApp usage)
2. gearpupm-core (comands like submit, kill, etc. plus master and worker)
3. gearpump-services 
3. experiments (storm, yarn, akka-streams)

Some details on experiments (AkkaApp usages):
```
gearpump-experiments-storm  (2 usages found)
org.apache.gearpump.experiments.storm.main  (2 usages found)
GearpumpNimbus.scala  (1 usage found)
47 object GearpumpNimbus extends AkkaApp with ArgumentsParser {
GearpumpStormClient.scala  (1 usage found)
27 object GearpumpStormClient extends AkkaApp with 
ArgumentsParser {
gearpump-experiments-yarn  (3 usages found)
org.apache.gearpump.experiments.yarn.appmaster  (1 usage found)
YarnAppMaster.scala  (1 usage found)
281 object YarnAppMaster extends AkkaApp with ArgumentsParser {
org.apache.gearpump.experiments.yarn.client  (2 usages found)
LaunchCluster.scala  (1 usage found)
160 object LaunchCluster extends AkkaApp with ArgumentsParser {
ManageCluster.scala  (1 usage found)
87 object ManageCluster extends AkkaApp with ArgumentsParser {
gearpump-servicesJVM  (1 usage found)
org.apache.gearpump.services.main  (1 usage found)
Services.scala  (1 usage found)
41 object Services extends AkkaApp with ArgumentsParser {
```

This is something I'd like to discuss. Do we change the ancestor here, too?
I need to refresh this yarn code in my head...




---

[GitHub] incubator-gearpump issue #241: [WiP][GEARPUMP-368] Restore setting runtime e...

2018-04-23 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/241
  
I did the initial version. Will test today.


---

[GitHub] incubator-gearpump issue #241: [WiP][GEARPUMP-368] Restore setting runtime e...

2018-04-23 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/241
  
One more thing to discuss:

In yarn code we already have a trait named `Command`:

experiments/yarn/src/main/scala/org/apache/gearpump/experiments/yarn/appmaster/Command.scala


Do we care (maybe we could rename the old one or find a "better" name for 
the new one) or we don't mind?


---

[jira] [Created] (GEARPUMP-372) Add tests for `gear` app submition

2018-04-05 Thread Karol Brejna (JIRA)

Karol Brejna created GEARPUMP-372:
-

 Summary: Add tests for `gear` app submition
 Key: GEARPUMP-372
 URL: https://issues.apache.org/jira/browse/GEARPUMP-372
 Project: Apache Gearpump
  Issue Type: Improvement
Reporter: Karol Brejna


When working on a fix I introduced a bug – `gear` was not able to submit an app 
to cluster. 

All the tests passed, though.

We need to add some tests for that case.

See: 
https://issues.apache.org/jira/browse/GEARPUMP-368?focusedCommentId=16426513=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16426513



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (GEARPUMP-368) Application details page does not load

2018-04-05 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426550#comment-16426550
 ] 

Karol Brejna edited comment on GEARPUMP-368 at 4/5/18 7:15 AM:
---

[~hashan] , you are right. I reproduce the problem with gear. "All green" tests 
it has lulled my vigilance.


was (Author: karol_brejna):
[~hashan] , you are right. I reproduce the problem with gear. "All grean" tests 
it has lulled my vigilance.

> Application details page does not load
> --
>
> Key: GEARPUMP-368
> URL: https://issues.apache.org/jira/browse/GEARPUMP-368
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.5
>Reporter: Hashan Gayasri Udugahapattuwa
>Assignee: Karol Brejna
>Priority: Major
> Attachments: gearpump-master-47505.log, gearpump-ui-47572.log, 
> gearpump-worker-47538.log, logs.zip
>
>
> Application details page does not load in the 
> 0.8.5-SNAPSHOT(8aac07b86d4b90e4f5118f3204610d3510f93b02). This is recreatable 
> with the default examples. 
> This issue not present in the 0.8.4 release.
>  
> Request : [http://172.25.34.11:8090/api/v1.0/appmaster/1?detail=true]
> Status Code : 500 Internal Server Error
>  
> Response : 
> akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://app1-executor-1@10.10.1.20:33881/user/daemon/appdaemon1/$c#1247996686]]
>  after [15000 ms]. Sender[null] sent message of type 
> "org.apache.gearpump.cluster.MasterToAppMaster$AppMasterDataDetailRequest".
>  at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:604)
>  at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:126)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
>  at 
> scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:599)
>  at 
> akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:329)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:280)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:284)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:236)
>  at java.lang.Thread.run(Unknown Source)
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEARPUMP-368) Application details page does not load

2018-04-05 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426550#comment-16426550
 ] 

Karol Brejna commented on GEARPUMP-368:
---

[~hashan] , you are right. I reproduce the problem with gear. "All grean" tests 
it has lulled my vigilance.

> Application details page does not load
> --
>
> Key: GEARPUMP-368
> URL: https://issues.apache.org/jira/browse/GEARPUMP-368
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.5
>Reporter: Hashan Gayasri Udugahapattuwa
>Assignee: Karol Brejna
>Priority: Major
> Attachments: gearpump-master-47505.log, gearpump-ui-47572.log, 
> gearpump-worker-47538.log, logs.zip
>
>
> Application details page does not load in the 
> 0.8.5-SNAPSHOT(8aac07b86d4b90e4f5118f3204610d3510f93b02). This is recreatable 
> with the default examples. 
> This issue not present in the 0.8.4 release.
>  
> Request : [http://172.25.34.11:8090/api/v1.0/appmaster/1?detail=true]
> Status Code : 500 Internal Server Error
>  
> Response : 
> akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://app1-executor-1@10.10.1.20:33881/user/daemon/appdaemon1/$c#1247996686]]
>  after [15000 ms]. Sender[null] sent message of type 
> "org.apache.gearpump.cluster.MasterToAppMaster$AppMasterDataDetailRequest".
>  at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:604)
>  at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:126)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
>  at 
> scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:599)
>  at 
> akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:329)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:280)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:284)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:236)
>  at java.lang.Thread.run(Unknown Source)
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (GEARPUMP-368) Application details page does not load

2018-04-05 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426536#comment-16426536
 ] 

Karol Brejna edited comment on GEARPUMP-368 at 4/5/18 6:58 AM:
---

[~mauzhang] , yes I was testing both finite and infinite examples (complex 
dag). For both tests deploying with UI doesn't work. Deploying with gear 
worked. I forgot we now have 2 version of wordcound, one of which (dsl) 
finishes quickly. Thank for reminding it ;)

 

[~hashan] , I was sure I tested gear submitting with success for basic examples 
(wordcount, complex dag). Let me retry with what you did.

 

 


was (Author: karol_brejna):
[~mauzhang] , yes I was testing both finite and infinite examples (complex 
dag). For both tests deploying with UI doesn't work. Deploying with gear 
worked. I forgot we now have 2 version of wordcound, one of which (dsl) 
finishes quickly. Thank for reminding it ;)

 

[~hashan] , I was testing gear submitting with success for basic examples 
(wordcount, complex dag). Let me retry with what you did.

 

 

> Application details page does not load
> --
>
> Key: GEARPUMP-368
> URL: https://issues.apache.org/jira/browse/GEARPUMP-368
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.5
>Reporter: Hashan Gayasri Udugahapattuwa
>    Assignee: Karol Brejna
>Priority: Major
> Attachments: gearpump-master-47505.log, gearpump-ui-47572.log, 
> gearpump-worker-47538.log, logs.zip
>
>
> Application details page does not load in the 
> 0.8.5-SNAPSHOT(8aac07b86d4b90e4f5118f3204610d3510f93b02). This is recreatable 
> with the default examples. 
> This issue not present in the 0.8.4 release.
>  
> Request : [http://172.25.34.11:8090/api/v1.0/appmaster/1?detail=true]
> Status Code : 500 Internal Server Error
>  
> Response : 
> akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://app1-executor-1@10.10.1.20:33881/user/daemon/appdaemon1/$c#1247996686]]
>  after [15000 ms]. Sender[null] sent message of type 
> "org.apache.gearpump.cluster.MasterToAppMaster$AppMasterDataDetailRequest".
>  at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:604)
>  at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:126)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
>  at 
> scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:599)
>  at 
> akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:329)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:280)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:284)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:236)
>  at java.lang.Thread.run(Unknown Source)
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEARPUMP-368) Application details page does not load

2018-04-05 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426536#comment-16426536
 ] 

Karol Brejna commented on GEARPUMP-368:
---

[~mauzhang] , yes I was testing both finite and infinite examples (complex 
dag). For both tests deploying with UI doesn't work. Deploying with gear 
worked. I forgot we now have 2 version of wordcound, one of which (dsl) 
finishes quickly. Thank for reminding it ;)

 

[~hashan] , I was testing gear submitting with success for basic examples 
(wordcount, complex dag). Let me retry with what you did.

 

 

> Application details page does not load
> --
>
> Key: GEARPUMP-368
> URL: https://issues.apache.org/jira/browse/GEARPUMP-368
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.5
>Reporter: Hashan Gayasri Udugahapattuwa
>    Assignee: Karol Brejna
>Priority: Major
> Attachments: gearpump-master-47505.log, gearpump-ui-47572.log, 
> gearpump-worker-47538.log, logs.zip
>
>
> Application details page does not load in the 
> 0.8.5-SNAPSHOT(8aac07b86d4b90e4f5118f3204610d3510f93b02). This is recreatable 
> with the default examples. 
> This issue not present in the 0.8.4 release.
>  
> Request : [http://172.25.34.11:8090/api/v1.0/appmaster/1?detail=true]
> Status Code : 500 Internal Server Error
>  
> Response : 
> akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://app1-executor-1@10.10.1.20:33881/user/daemon/appdaemon1/$c#1247996686]]
>  after [15000 ms]. Sender[null] sent message of type 
> "org.apache.gearpump.cluster.MasterToAppMaster$AppMasterDataDetailRequest".
>  at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:604)
>  at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:126)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
>  at 
> scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:599)
>  at 
> akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:329)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:280)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:284)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:236)
>  at java.lang.Thread.run(Unknown Source)
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] incubator-gearpump pull request #241: [GEARPUMP-368] Restore setting runtime...

2018-04-04 Thread karol-brejna-i

GitHub user karol-brejna-i opened a pull request:

https://github.com/apache/incubator-gearpump/pull/241

[GEARPUMP-368] Restore setting runtime env

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

 - [x] Make sure the commit message is formatted like:
   `[GEARPUMP-] Meaningful description of pull request` 
 - [x] Make sure tests pass via `sbt clean test`.
 - [x] Make sure old documentation affected by the pull request has been 
updated and new documentation added for new functionality. 



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

$ git pull https://github.com/karol-brejna-i/incubator-gearpump 
GEARPUMP-368_submit_app_via_ui

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

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


commit 7fabcafcd58c39d99a669ddf9cbc3e0e38221978
Author: karol-brejna-i <karol.brejna@...>
Date:   2018-04-04T13:54:49Z

[GEARPUMP-368] Restore setting runtime env




---

[GitHub] incubator-gearpump issue #241: [GEARPUMP-368] Restore setting runtime env

2018-04-04 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/241
  
Two unrelated test fail:
```
[info] *** 2 TESTS FAILED ***
[error] Failed: Total 35, Failed 2, Errors 0, Passed 33
[error] Failed tests:
[error] 
org.apache.gearpump.services.security.oauth2.GoogleOAuth2AuthenticatorSpec
[error] 
org.apache.gearpump.services.security.oauth2.CloudFoundryUAAOAuth2AuthenticatorSpec
```

One additional test fail:

```
[info] *** 1 TEST FAILED ***
[error] Failed: Total 88, Failed 1, Errors 0, Passed 87
[error] Failed tests:
[error] org.apache.gearpump.cluster.main.MainSpec
```


---

[jira] [Created] (GEARPUMP-371) Introduce [basic] UI tests

2018-04-04 Thread Karol Brejna (JIRA)

Karol Brejna created GEARPUMP-371:
-

 Summary: Introduce [basic] UI tests
 Key: GEARPUMP-371
 URL: https://issues.apache.org/jira/browse/GEARPUMP-371
 Project: Apache Gearpump
  Issue Type: Improvement
Reporter: Karol Brejna


Due to problems like https://issues.apache.org/jira/browse/GEARPUMP-368 I think 
having some basic UI tests (automats that "walk" on the web pages) would be 
beneficial.

Some simple things like:
 * submitting an app
 * destroying an app
 * dynamic dag modification

would be a good start.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEARPUMP-368) Application details page does not load

2018-04-04 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425425#comment-16425425
 ] 

Karol Brejna commented on GEARPUMP-368:
---

This commit seems to be the cause of the problem: 
https://github.com/apache/incubator-gearpump/commit/2d2f279533a221c7b9317440a13cd2570267b85e

> Application details page does not load
> --
>
> Key: GEARPUMP-368
> URL: https://issues.apache.org/jira/browse/GEARPUMP-368
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.5
>Reporter: Hashan Gayasri Udugahapattuwa
>    Assignee: Karol Brejna
>Priority: Major
> Attachments: gearpump-master-47505.log, gearpump-ui-47572.log, 
> gearpump-worker-47538.log
>
>
> Application details page does not load in the 
> 0.8.5-SNAPSHOT(8aac07b86d4b90e4f5118f3204610d3510f93b02). This is recreatable 
> with the default examples. 
> This issue not present in the 0.8.4 release.
>  
> Request : [http://172.25.34.11:8090/api/v1.0/appmaster/1?detail=true]
> Status Code : 500 Internal Server Error
>  
> Response : 
> akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://app1-executor-1@10.10.1.20:33881/user/daemon/appdaemon1/$c#1247996686]]
>  after [15000 ms]. Sender[null] sent message of type 
> "org.apache.gearpump.cluster.MasterToAppMaster$AppMasterDataDetailRequest".
>  at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:604)
>  at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:126)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
>  at 
> scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:599)
>  at 
> akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:329)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:280)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:284)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:236)
>  at java.lang.Thread.run(Unknown Source)
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEARPUMP-368) Application details page does not load

2018-04-04 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425267#comment-16425267
 ] 

Karol Brejna commented on GEARPUMP-368:
---

[~hashan] , thanks for the report. I think I was able to reproduce the problem. 

> Application details page does not load
> --
>
> Key: GEARPUMP-368
> URL: https://issues.apache.org/jira/browse/GEARPUMP-368
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.5
>Reporter: Hashan Gayasri Udugahapattuwa
>    Assignee: Karol Brejna
>Priority: Major
> Attachments: gearpump-master-47505.log, gearpump-ui-47572.log, 
> gearpump-worker-47538.log
>
>
> Application details page does not load in the 
> 0.8.5-SNAPSHOT(8aac07b86d4b90e4f5118f3204610d3510f93b02). This is recreatable 
> with the default examples. 
> This issue not present in the 0.8.4 release.
>  
> Request : [http://172.25.34.11:8090/api/v1.0/appmaster/1?detail=true]
> Status Code : 500 Internal Server Error
>  
> Response : 
> akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://app1-executor-1@10.10.1.20:33881/user/daemon/appdaemon1/$c#1247996686]]
>  after [15000 ms]. Sender[null] sent message of type 
> "org.apache.gearpump.cluster.MasterToAppMaster$AppMasterDataDetailRequest".
>  at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:604)
>  at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:126)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
>  at 
> scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:599)
>  at 
> akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:329)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:280)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:284)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:236)
>  at java.lang.Thread.run(Unknown Source)
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEARPUMP-368) Application details page does not load

2018-04-04 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425261#comment-16425261
 ] 

Karol Brejna commented on GEARPUMP-368:
---

Looks like there is indeed something wrong.

Checked wordcount example (gearpump-examples-wordcount and complexdag). In the 
logs (ui) I see the app starts to run and then finishes:
{code:java}
2018-04-04 10:34:26,709 INFO redirect: [AppManager] Application 1 change to 
active at 1522830866705
2018-04-04 10:34:26,710 INFO redirect: [AppMaster@app1] AppMaster for app1 is 
activated
2018-04-04 10:34:27,343 INFO redirect: 
(is,1)(bingo!!,2)(a,1)(good,1)(This,1)(start,,1)[AppManager] Application 1 
change to succeeded at 1522830867340
2018-04-04 10:34:27,343 INFO redirect: [AppManager] Shutdown AppMaster at 
akka://master/user/Worker0, appId: 1, executorId: -1
2018-04-04 10:34:27,343 INFO redirect: [Worker@workerWorkerId(0,1522830864990)] 
Shutdown executor app1-executor-1(akka://master/user/Worker0/$c) due to: 
AppMaster 1 shutdown requested by master...
2018-04-04 10:34:27,344 INFO redirect: [RunningApplication$] Application 1 
succeeded{code}
 applicationData folder is not created at all. 

Will investigate further.

 

> Application details page does not load
> --
>
> Key: GEARPUMP-368
> URL: https://issues.apache.org/jira/browse/GEARPUMP-368
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.5
>Reporter: Hashan Gayasri Udugahapattuwa
>    Assignee: Karol Brejna
>Priority: Major
> Attachments: gearpump-master-47505.log, gearpump-ui-47572.log, 
> gearpump-worker-47538.log
>
>
> Application details page does not load in the 
> 0.8.5-SNAPSHOT(8aac07b86d4b90e4f5118f3204610d3510f93b02). This is recreatable 
> with the default examples. 
> This issue not present in the 0.8.4 release.
>  
> Request : [http://172.25.34.11:8090/api/v1.0/appmaster/1?detail=true]
> Status Code : 500 Internal Server Error
>  
> Response : 
> akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://app1-executor-1@10.10.1.20:33881/user/daemon/appdaemon1/$c#1247996686]]
>  after [15000 ms]. Sender[null] sent message of type 
> "org.apache.gearpump.cluster.MasterToAppMaster$AppMasterDataDetailRequest".
>  at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:604)
>  at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:126)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
>  at 
> scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:599)
>  at 
> akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:329)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:280)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:284)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:236)
>  at java.lang.Thread.run(Unknown Source)
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEARPUMP-368) Application details page does not load

2018-04-04 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-368:
--
Attachment: gearpump-worker-47538.log
gearpump-ui-47572.log
gearpump-master-47505.log

> Application details page does not load
> --
>
> Key: GEARPUMP-368
> URL: https://issues.apache.org/jira/browse/GEARPUMP-368
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.5
>Reporter: Hashan Gayasri Udugahapattuwa
>    Assignee: Karol Brejna
>Priority: Major
> Attachments: gearpump-master-47505.log, gearpump-ui-47572.log, 
> gearpump-worker-47538.log
>
>
> Application details page does not load in the 
> 0.8.5-SNAPSHOT(8aac07b86d4b90e4f5118f3204610d3510f93b02). This is recreatable 
> with the default examples. 
> This issue not present in the 0.8.4 release.
>  
> Request : [http://172.25.34.11:8090/api/v1.0/appmaster/1?detail=true]
> Status Code : 500 Internal Server Error
>  
> Response : 
> akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://app1-executor-1@10.10.1.20:33881/user/daemon/appdaemon1/$c#1247996686]]
>  after [15000 ms]. Sender[null] sent message of type 
> "org.apache.gearpump.cluster.MasterToAppMaster$AppMasterDataDetailRequest".
>  at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:604)
>  at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:126)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
>  at 
> scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:599)
>  at 
> akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:329)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:280)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:284)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:236)
>  at java.lang.Thread.run(Unknown Source)
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (GEARPUMP-368) Application details page does not load

2018-04-04 Thread Karol Brejna (JIRA)


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

Karol Brejna reassigned GEARPUMP-368:
-

Assignee: Karol Brejna

> Application details page does not load
> --
>
> Key: GEARPUMP-368
> URL: https://issues.apache.org/jira/browse/GEARPUMP-368
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.5
>Reporter: Hashan Gayasri Udugahapattuwa
>    Assignee: Karol Brejna
>Priority: Major
>
> Application details page does not load in the 
> 0.8.5-SNAPSHOT(8aac07b86d4b90e4f5118f3204610d3510f93b02). This is recreatable 
> with the default examples. 
> This issue not present in the 0.8.4 release.
>  
> Request : [http://172.25.34.11:8090/api/v1.0/appmaster/1?detail=true]
> Status Code : 500 Internal Server Error
>  
> Response : 
> akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://app1-executor-1@10.10.1.20:33881/user/daemon/appdaemon1/$c#1247996686]]
>  after [15000 ms]. Sender[null] sent message of type 
> "org.apache.gearpump.cluster.MasterToAppMaster$AppMasterDataDetailRequest".
>  at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:604)
>  at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:126)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
>  at 
> scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:599)
>  at 
> akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:329)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:280)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:284)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:236)
>  at java.lang.Thread.run(Unknown Source)
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] incubator-gearpump issue #233: [GEARPUMP-361] Build gearpump docker image lo...

2017-10-27 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/233
  
The third problem - works for me on Ubuntu 16.04. 

```
[DEBUG] [05:25:55.233] [Docker$] Container master0>> curl 
http://master0:8090/api/v1.0/master
[DEBUG] [05:25:55.233] [Docker$] INPUT==>>
[DEBUG] [05:25:55.233] [ShellExec$] EXEC master0 => `docker exec master0 
curl -s  --cookie cookie.txt http://master0:8090/api/v1.0/master`
[DEBUG] [05:25:55.379] [ShellExec$] EXEC master0 <= 
`{"masterDescription":{"leader":{"host":"master@master0","port":3000},"cluster":[{"host":"master0","port":3000}],"aliveFor":"8068","logFile":"/opt/gearpump/var/log/gearpump/daemon","jarStore":"jarstore...`
 exit 0
[DEBUG] [05:25:55.379] [Docker$] <<==OUTPUT
```
Checking on Mac...


---

[GitHub] incubator-gearpump pull request #233: [GEARPUMP-361] Build gearpump docker i...

2017-10-27 Thread karol-brejna-i

Github user karol-brejna-i commented on a diff in the pull request:

https://github.com/apache/incubator-gearpump/pull/233#discussion_r147378048
  
--- Diff: integrationtest/docker/gearpump/Dockerfile ---
@@ -18,7 +18,8 @@
 FROM openjdk:8u131-jre-alpine
 
 # Install python
-RUN apk add --no-cache python && \
+RUN apk add --update curl && \
--- End diff --

please, use `apk add --update curl python` (one line)


---

[GitHub] incubator-gearpump issue #233: [GEARPUMP-361] Build gearpump docker image lo...

2017-10-27 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/233
  
```[DEBUG] [13:07:44.774] [Docker$] Container master0>> curl 
http://master0:8090/api/v1.0/master
[DEBUG] [13:07:44.774] [Docker$] INPUT==>>
[DEBUG] [13:07:44.775] [ShellExec$] EXEC master0 => `docker exec master0 
curl -s  --cookie cookie.txt http://master0:8090/api/v1.0/master`
[DEBUG] [13:07:45.490] [ShellExec$] EXEC master0 <= 
`{"masterDescription":{"leader":{"host":"master@master0","port":3000},"cluster":[{"host":"master0","port":3000}],"aliveFor":"18124","logFile":"/opt/gearpump/logs","jarStore":"jarstore/","masterStatus":...`
 exit 0
[DEBUG] [13:07:45.490] [Docker$] <<==OUTPUT
[DEBUG] [13:07:45.490] [Docker$] 
{"masterDescription":{"leader":{"host":"master@master0","port":3000},"cluster":[{"host":"master0","port":3000}],"aliveFor":"18124","logFile":"/opt/gearpump/logs","jarStore":"jarstore/","masterStatus":"synced","homeDirectory":"/opt/gearpump","activities":[],"jvmName":"7@master0","historyMetricsConfig":{"retainHistoryDataHours":72,"retainHistoryDataIntervalMs":360,"retainRecentDataSeconds":300,"retainRecentDataIntervalMs":15000}}}
[DEBUG] [13:07:45.491] [Docker$] <<Command END. Container master0, curl 
http://master0:8090/api/v1.0/master 
```

Number 3 looks good on mac, too. For me it seems like some proxy-caused 
redirect...


---

[GitHub] incubator-gearpump issue #233: [WIP] Fix integration test

2017-10-26 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/233
  
Docker image problem solved with 
https://github.com/apache/incubator-gearpump/pull/235.


---

[GitHub] incubator-gearpump issue #235: Use alpine-based image for gearpump-runner

2017-10-26 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/235
  
done!


---

[GitHub] incubator-gearpump pull request #235: Use alpine-based image for gearpump-ru...

2017-10-26 Thread karol-brejna-i

GitHub user karol-brejna-i opened a pull request:

https://github.com/apache/incubator-gearpump/pull/235

Use alpine-based image for gearpump-runner

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

 - [ ] Make sure the commit message is formatted like:
   `[GEARPUMP-] Meaningful description of pull request` 
 - [ ] Make sure tests pass via `sbt clean test`.
 - [ ] Make sure old documentation affected by the pull request has been 
updated and new documentation added for new functionality. 

To verify:
1. build the image (`docker build --build-arg HTTP_PROXY=$http_proxy 
--build-arg HTTPS_PROXY=$https_proxy -t gearpump/gearpump-launcher 
integrationtest/docker/gearpump/
`)
2. run the master (`docker run -d -h master0 -v 
/etc/localtime:/etc/localtime:ro -p 8090:8090 -e 
JAVA_OPTS=-Dgearpump.cluster.masters.0=master0:3000 -v 
$GEARPUMP_HOME:/opt/gearpump -v /tmp/gearpump:/var/log/gearpump --name master0 
gearpump/gearpump-launcher master -ip master0 -port 3000` - please, mind it 
tries to use the port 8090)
3. run the worker (`docker run -d -h worker0 -v 
/etc/localtime:/etc/localtime:ro -e 
JAVA_OPTS=-Dgearpump.cluster.masters.0=master0:3000 -v 
$GEARPUMP_HOME:/opt/gearpump -v /tmp/gearpump:/var/log/gearpump --link master0 
--name worker0 gearpump/gearpump-launcher worker`)
4. verify it works (`docker logs master0`, `docker logs worker0`, open 
localhost:8090 in the browser)

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

$ git pull https://github.com/karol-brejna-i/incubator-gearpump 
GEARPUMP-360-fix-dockerfile

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

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


commit 6a85a6a1b362cbaafd85cd7b02439b58272a59e1
Author: karol-brejna-i <karol.bre...@intel.com>
Date:   2017-10-26T09:20:08Z

Use alpine-based image for gearpump-runner




---

[jira] [Updated] (GEARPUMP-360) gearpump-launcher image broken

2017-10-26 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-360:
--
Fix Version/s: 0.8.5

> gearpump-launcher image broken
> --
>
> Key: GEARPUMP-360
> URL: https://issues.apache.org/jira/browse/GEARPUMP-360
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: integrationtest
>Affects Versions: 0.8.4
>Reporter: Karol Brejna
>    Assignee: Karol Brejna
> Fix For: 0.8.5
>
>
> Building docker image for integration tests fails:
> {code}
> > docker build --no-cache -t gearpump/gearpump-launcher 
> > integrationtest/docker/gearpump
> Sending build context to Docker daemon  8.192kB
> Step 1/7 : FROM grubykarol/jre:8u121b13_server
>  ---> f7e482e81614
> Step 2/7 : RUN opkg-install python
>  ---> Running in 0939e0c36efc
> Downloading 
> http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/base/Packages.gz.
> Inflating 
> http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/base/Packages.gz.
> Updated list of available packages in /var/opkg-lists/base.
> Downloading 
> http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/packages/Packages.gz.
> Inflating 
> http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/packages/Packages.gz.
> Updated list of available packages in /var/opkg-lists/packages.
> Unknown package 'python'.
> Collected errors:
>  *opkg_install_cmd: Cannot install package python.
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEARPUMP-360) gearpump-launcher image broken

2017-10-26 Thread Karol Brejna (JIRA)

Karol Brejna created GEARPUMP-360:
-

 Summary: gearpump-launcher image broken
 Key: GEARPUMP-360
 URL: https://issues.apache.org/jira/browse/GEARPUMP-360
 Project: Apache Gearpump
  Issue Type: Bug
  Components: integrationtest
Affects Versions: 0.8.4
Reporter: Karol Brejna
Assignee: Karol Brejna


Building docker image for integration tests fails:

{code}
> docker build --no-cache -t gearpump/gearpump-launcher 
> integrationtest/docker/gearpump


Sending build context to Docker daemon  8.192kB
Step 1/7 : FROM grubykarol/jre:8u121b13_server
 ---> f7e482e81614
Step 2/7 : RUN opkg-install python
 ---> Running in 0939e0c36efc
Downloading 
http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/base/Packages.gz.
Inflating 
http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/base/Packages.gz.
Updated list of available packages in /var/opkg-lists/base.
Downloading 
http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/packages/Packages.gz.
Inflating 
http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/packages/Packages.gz.
Updated list of available packages in /var/opkg-lists/packages.
Unknown package 'python'.
Collected errors:
 *opkg_install_cmd: Cannot install package python.
{code}





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-gearpump issue #233: [WIP] Fix integration test

2017-10-24 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/233
  
I've just confirmed. The problem persists, even when networking/proxy 
problems are overcomed:

```
$ docker build --no-cache -t gearpump/gearpump-launcher 
integrationtest/docker/gearpump
Sending build context to Docker daemon  8.192kB
Step 1/7 : FROM grubykarol/jre:8u121b13_server
 ---> f7e482e81614
Step 2/7 : RUN opkg-install python
 ---> Running in 0939e0c36efc
Downloading 
http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/base/Packages.gz.
Inflating 
http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/base/Packages.gz.
Updated list of available packages in /var/opkg-lists/base.
Downloading 
http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/packages/Packages.gz.
Inflating 
http://downloads.openwrt.org/snapshots/trunk/x86/64/packages/packages/Packages.gz.
Updated list of available packages in /var/opkg-lists/packages.
Unknown package 'python'.
Collected errors:
 * opkg_install_cmd: Cannot install package python.
```


`Unknown package 'python'.` 


---

[GitHub] incubator-gearpump issue #233: [WIP] Fix integration test

2017-10-24 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/233
  
Even when providing proxy args for docker build:
```
docker build --no-cache --build-arg HTTP_PROXY=$http_proxy --build-arg 
HTTPS_PROXY=$https_proxy -t gearpump/gearpump-launcher 
integrationtest/docker/gearpump
```

It still fails to install python. I'll try to find a workaround for this.


---

[GitHub] incubator-gearpump issue #230: [GEARPUMP-354] Fix the tracking url resolutio...

2017-10-11 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/230
  
@titikakatoo Please advise on quick/easy validation procedure. Also: Do you 
know any way to have kerberized yarn running in docker? 


---

[jira] [Created] (GEARPUMP-352) "License" should link to: http://www.apache.org/licenses/

2017-10-05 Thread Karol Brejna (JIRA)

Karol Brejna created GEARPUMP-352:
-

 Summary: "License" should link to: http://www.apache.org/licenses/
 Key: GEARPUMP-352
 URL: https://issues.apache.org/jira/browse/GEARPUMP-352
 Project: Apache Gearpump
  Issue Type: Bug
  Components: doc
Affects Versions: 0.8.4
Reporter: Karol Brejna
Assignee: Karol Brejna
Priority: Trivial


APACHE PROJECT WEBSITE BRANDING POLICY
notes (among others) that "License" should link to: 
http://www.apache.org/licenses/.

We link to http://gearpump.apache.org/license.html (from apache.gearpump.org).

Review other requirements and verify if we meet them.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[ANNOUNCE] Apache Gearpump 0.8.4-incubating Release

2017-07-10 Thread Karol Brejna

The Apache Gearpump team would like to announce the release of Apache
Gearpump 0.8.4-incubating.

Apache Gearpump (incubating) is a reactive real-time streaming engine based
on the micro-service Actor model. It provides extremely high performance
stream processing while maintaining millisecond latency message delivery.
Apache Gearpump (incubating) enables reusable, composable flows or partial
graphs that can be remotely deployed and executed in a diverse set of
environments. These flows may be deployed and modified at runtime.

More details regarding Apache Gearpump (incubating) can be found here:
http://gearpump.apache.org/

The release artifacts can be downloaded here:
https://dist.apache.org/repos/dist/release/incubator/gearpump/0.8.4-incubating/

The ChangeLog can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319920=12340225

The Maven artifacts are published to
https://repository.apache.org/content/repositories/releases/org/apache/gearpump/
(and can be found on Maven Central, too:
http://central.maven.org/maven2/org/apache/gearpump/).

Thanks!
The Apache Gearpump (incubating) Team

DISCLAIMER
Apache Gearpump (incubating) is an effort undergoing incubation at the
Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects. While incubation status is not necessarily a reflection of
the completeness or stability of the code, it does indicate that the
project has yet to be fully endorsed by the ASF.

[RESULT][VOTE] Apache Gearpump (incubating) 0.8.4-RC1

2017-07-06 Thread Karol Brejna

Dear IPMC Community,

I am pleased to announce that the Incubator PMC has approved 0.8.4-RC1
of Apache Gearpump (Incubating) for release as version 0.8.4 (Incubating).

The vote has passed with:
- three binding "+1" votes
- no "0" votes
- no "-1" votes

The votes were 
(https://www.mail-archive.com/general@incubator.apache.org/msg59297.html):
- +1, Justin Mclean (binding)
- +1, Jean-Baptiste Onofré (binding)
- +1, Andrew Purtell (binding)

Thank you, for your support!

We'll continue with the release now.

Karol,
on behalf of Apache Gearpump PPMC

[VOTE] Release of Apache Gearpump 0.8.4-incubating, release candidate #1

2017-06-26 Thread Karol Brejna

The time is up. It looks like we have the quorum.

The voting passes with clean 3 times +1 votes (no "0", no "-1") from
* Jean-Baptiste Onofré
* Vincent Wang
* Manu Zhang

Thank You for participating.

Let me continue with the release process.
(Process the voting on IPMC Community list.)

Regards,
Karol

[VOTE] Release of Apache Gearpump 0.8.3-incubating, release candidate #1

2017-06-23 Thread Karol Brejna

Hi Gearpump Community,

This is a call for a discussion releasing Apache Gearpump
0.8.4-incubating, release candidate #1, which leitmotiv is Apache Beam
integration.

The source and binary tarballs, including signatures, digests, etc.
can be found at:
https://dist.apache.org/repos/dist/dev/incubator/gearpump/0.8.4-incubating/RC1/

Release artifacts are signed with the key with fingerprint:
3F12 81A2 DB58 0842 5ABA  6962 D8A8 4FBC 0A83 B291

The KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/gearpump/KEYS

The tag to be voted upon is:
https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=shortlog;h=refs/tags/0.8.4-RC1

The release hash is:
https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=commit;h=71132b256b8edbd734839386d8de2731813bd290

For information about the contents of this release see:
https://issues.apache.org/jira/projects/GEARPUMP/versions/12340225

This vote will be open for 72 hours (Monday, April 27, 2017 at 4:00PM PST).

Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, run the
binary artifacts in the binary release and test.
Please vote:

[ ] +1 Release this package as gearpump-0.8.4
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

Thanks,
Karol

[jira] [Updated] (GEARPUMP-206) access to upstream and downstream processors

2017-06-23 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-206:
--
Fix Version/s: (was: 0.8.4)
   0.8.5

> access to upstream and downstream processors
> 
>
> Key: GEARPUMP-206
> URL: https://issues.apache.org/jira/browse/GEARPUMP-206
> Project: Apache Gearpump
>  Issue Type: Sub-task
>Affects Versions: 0.8.1
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
> Fix For: 0.8.5
>
>
> akka-streams requires the ability to access both upstream and downstream 
> processors. For upstream akka-streams will pull - we need to emulate 
> something similar



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (GEARPUMP-22) Support akka-streams Gearpump Materializer

2017-06-23 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-22:
-
Fix Version/s: (was: 0.8.4)
   0.8.5

> Support akka-streams Gearpump Materializer
> --
>
> Key: GEARPUMP-22
> URL: https://issues.apache.org/jira/browse/GEARPUMP-22
> Project: Apache Gearpump
>  Issue Type: New Feature
>  Components: akkastream
>Affects Versions: 0.8.0
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
> Fix For: 0.8.5
>
>
> Reenable experiments/akkastream to work with akka 2.4.3 (latest on master)
> Create PR's for akka team related to changes required for Gearpump 
> Materializer



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (GEARPUMP-191) add ability to control rate to TaskActor

2017-06-23 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-191:
--
Fix Version/s: (was: 0.8.4)
   0.8.5

> add ability to control rate to TaskActor
> 
>
> Key: GEARPUMP-191
> URL: https://issues.apache.org/jira/browse/GEARPUMP-191
> Project: Apache Gearpump
>  Issue Type: Sub-task
>Affects Versions: 0.8.1
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
> Fix For: 0.8.5
>
>
> akka-streams requires an ability to control the rate of input and output of 
> messages within a task. See Throttle 
> (http://doc.akka.io/docs/akka/current/scala/stream/stream-quickstart.html#Time-Based_Processing)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (GEARPUMP-190) Add logo with text to site

2017-06-23 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-190:
--
Fix Version/s: (was: 0.8.4)
   0.8.5

> Add logo with text to site
> --
>
> Key: GEARPUMP-190
> URL: https://issues.apache.org/jira/browse/GEARPUMP-190
> Project: Apache Gearpump
>  Issue Type: Task
>Affects Versions: 0.8.1
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
>Priority: Minor
> Fix For: 0.8.5
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: svn dev repo cleanups

2017-06-23 Thread Karol Brejna

(continued)

... the artifacts from
https://dist.apache.org/repos/dist/dev/incubator/gearpump'  to
https://dist.apache.org/repos/dist/release/incubator/gearpump/ repo,
so we don't loose any historical data.

The situation is worse when we have multiple release
candidates.Erasing the old artifacts would quicken the release
procedure.

Please, tell me what you think.

Karol

On Fri, Jun 23, 2017 at 6:59 PM, Karol Brejna <karolbre...@apache.org> wrote:
> I am preparing artifacts for 0.8.4 release.
>
> On of the steps is to publish them to svn.
> In order to publish, you need to check out svn repo (which in turn
> pull all files stored there).
>
> The files got quite sizeble:
>
> 575180  gearpump/.svn
> 185280  gearpump/0.8.2-incubating
> 245708  gearpump/0.8.3-incubating
>
>
> So it's about 1GB worth of files which transfer takes quite a long time.
>
> I am proposing enriching our release procedure with a step of cleaning
> release artifacts after the release.
>
> After release we move

svn dev repo cleanups

2017-06-23 Thread Karol Brejna

I am preparing artifacts for 0.8.4 release.

On of the steps is to publish them to svn.
In order to publish, you need to check out svn repo (which in turn
pull all files stored there).

The files got quite sizeble:

575180  gearpump/.svn
185280  gearpump/0.8.2-incubating
245708  gearpump/0.8.3-incubating


So it's about 1GB worth of files which transfer takes quite a long time.

I am proposing enriching our release procedure with a step of cleaning
release artifacts after the release.

After release we move

Re: Podling Report Reminder - June 2017

2017-06-05 Thread Karol Brejna

Manu,

Do we mention the effort on akka-streams integration?

Otherwise, looks good.

Karol

On Mon, Jun 5, 2017 at 3:13 AM, Manu Zhang  wrote:
> Hi all,
>
> Here is the Gearpump Podling Report. Please review.
>
>  Gearpump
>
>  Gearpump is a reactive real-time streaming engine based on the
> micro-service Actor model.
>  Gearpump has been incubating since 2016-03-08.
>
>  Three most important issues to address in the move towards graduation:
>
>  1. Make initial Apache branded release and release on a regular schedule.
>  2. Continue to evolve community interest and support.
>  3. Integrate within Apache Beam and akka-stream frameworks.
>
>  - Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware
>  of?
>  - None.
>
>
>  - How has the community developed since the last report?
>  - Increased community contribution on rabbitmq connector and state
> management.
>
>  - How has the project developed since the last report?
>  - 27 issues created and 24 issues resolved.
>  - Continued integration within Apache Beam (Gearpump Runner).
>  - Joined in GSoC 2017 project.
>
>  Date of last release:
>  2017-04-19
>
>
>  When were the last committers or PMC members elected?
>  No new committers or PMC members elected yet.
>
>  Signed-off-by:
>
>  [ ](gearpump) Jean-Baptiste Onofré
>  [ ](gearpump) Andrew Purtell
>  [ ](gearpump) Jarek Jarcec Cecho
>  [ ](gearpump) Reynold Xin
>  [ ](gearpump) Todd Lipcon
>  [ ](gearpump) Xuefu Zhang
>
> On Mon, Jun 5, 2017 at 6:19 AM  wrote:
>
>> 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, 21 June 2017, 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, June 07).
>>
>> 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.
>> *   How does the podling rate their own maturity.
>>
>> This should be appended to the Incubator Wiki page at:
>>
>> https://wiki.apache.org/incubator/June2017
>>
>> 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] [Commented] (GEARPUMP-167) Create Elasticsearch sink and example

2017-05-10 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004425#comment-16004425
 ] 

Karol Brejna commented on GEARPUMP-167:
---

[~yanghua] I started developing PoC on the following branch: 
https://github.com/karol-brejna-i/incubator-gearpump/tree/GEARPUMP-167-elasticsearch-sink

My idea was to have a simple sink that would just accept a JSON document to be 
stored in elasticsearch (not an object that would need to be serialized to 
JSON).

I anticipated two cases for the incoming message:
* Tuple2[String, String] - id, body - message gets stored under given id, so 
it's actually an upsert 
* String - body - message is stored under new id
* A sequence of any of above

I even did some short "demo" that had:
* small app subscribing to Twitter and putting messages to Kafka
* a DAG that consumed messages from Kafka, did wordcount, stored data to 
elasticsearch
* Kibana visualization


The code was written in Java. I planned to convert it to Scala but got 
distracted by the last release...

[~yanghua] I'd be glad to hear your idea on this. Maybe we could cooperate on 
this feature.

> Create Elasticsearch sink and example
> -
>
> Key: GEARPUMP-167
> URL: https://issues.apache.org/jira/browse/GEARPUMP-167
> Project: Apache Gearpump
>  Issue Type: Task
>  Components: connectors
>Reporter: Karol Brejna
>Assignee: Karol Brejna
>  Labels: feature
>   Original Estimate: 18h
>  Remaining Estimate: 18h
>
> Create a simple Elasticsearch sink that enables indexing messages as 
> Elasticsearch docs.
> Write an example demonstrating usage of the sink
> Write a doc on setting up local development env (installing and confifuring 
> elastic, etc.) for the users of the sink



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: IntelliJ IDEA licence expired

2017-05-10 Thread Karol Brejna

I'll write to JetBrains today and ask for renewal for Gearpump project.

W dniu śr., 10.05.2017 o 03:40 Vincent Wang <fvunic...@gmail.com>
napisał(a):

> Hi Karol, I also noticed that. I tried to renew it but didn't find out how
> to do that. Eventually I found that I can get a license using my apache
> membership （email account).
>
> Karol Brejna <karolbre...@apache.org>于2017年5月9日周二 下午4:43写道：
>
> > I've just noticed, that our IntelliJ license for Gearpump has expired.
> >
> > My license details:
> >
> > Licensed to: GearPump
> > License restriction: For non-commercial open source development only
> > Valid through: April 21, 2017
> >
> > Do you remember how to renew the license with JetBrains?
> >
> > Regards,
> > Karol
> >
>

[jira] [Commented] (GEARPUMP-284) Oauth2 tests fail

2017-05-09 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002448#comment-16002448
 ] 

Karol Brejna commented on GEARPUMP-284:
---


>From my observation, the test that fails is: 
>services/jvm/src/test/scala/org/apache/gearpump/services/security/oauth2/GoogleOAuth2AuthenticatorSpec.scala

The test tries to authenticate against google OAuth server.

The log relevant for the error is:
{code}
ExecutorSystemLauncherSpec:^[[0m^[[0m
- should report success when worker launch the system successfully^[[0m^[[0m
- should report failure when worker refuse to launch the system 
explicitly^[[0m^[[0m
- should report timeout when trying to start a executor system on worker, and 
worker doesn't response^[[0m^[[0m
CloudFoundryUAAOAuth2AuthenticatorSpec:^[[0m^[[0m
- should generate the correct authorization request^[[0m^[[0m
- should authenticate the authorization code and return the correct profile *** 
FAILED ***^[[0m^[[0m
  com.github.scribejava.core.exceptions.OAuthException: Response body is 
incorrect. Can't extract a '"access_token"\s*:\s*"(\S*?)"' from this: 
'^M^[[0m^[[0m
Redirection^M^[[0m^[[0m
Redirect^M^[[0m^[[0m
'^[[0m^[[0m
  at 
com.github.scribejava.core.extractors.OAuth2AccessTokenJsonExtractor.extractParameter(OAuth2AccessTokenJsonExtractor.java:64)^[[0m^[[0m
  at 
com.github.scribejava.core.extractors.OAuth2AccessTokenJsonExtractor.extract(OAuth2AccessTokenJsonExtractor.java:37)^[[0m^[[0m
  at 
com.github.scribejava.core.extractors.OAuth2AccessTokenJsonExtractor.extract(OAuth2AccessTokenJsonExtractor.java:12)^[[0m^[[0m
  at 
com.github.scribejava.core.oauth.OAuth20Service$1.convert(OAuth20Service.java:47)^[[0m^[[0m
  at 
com.github.scribejava.core.oauth.OAuth20Service$1.convert(OAuth20Service.java:43)^[[0m^[[0m
  at 
com.github.scribejava.core.model.OAuthRequestAsync$OAuthAsyncCompletionHandler.onCompleted(OAuthRequestAsync.java:104)^[[0m^[[0m
  at 
com.ning.http.client.AsyncCompletionHandler.onCompleted(AsyncCompletionHandler.java:55)^[[0m^[[0m
  at 
com.ning.http.client.providers.netty.future.NettyResponseFuture.getContent(NettyResponseFuture.java:177)^[[0m^[[0m
  at 
com.ning.http.client.providers.netty.future.NettyResponseFuture.done(NettyResponseFuture.java:214)^[[0m^[[0m
  at 
com.ning.http.client.providers.netty.handler.HttpProtocol.finishUpdate(HttpProtocol.java:194)^[[0m^[[0m
  ...^[[0m^[[0m
GoogleOAuth2AuthenticatorSpec:^[[0m^[[0m
- should generate the correct authorization request^[[0m^[[0m
- should authenticate the authorization code and return the correct profile *** 
FAILED ***^[[0m^[[0m
  com.github.scribejava.core.exceptions.OAuthException: Response body is 
incorrect. Can't extract a '"access_token"\s*:\s*"(\S*?)"' from this: 
'^M^[[0m^[[0m
Redirection^M^[[0m^[[0m
Redirect^M^[[0m^[[0m
'^[[0m^[[0m
  at 
com.github.scribejava.core.extractors.OAuth2AccessTokenJsonExtractor.extractParameter(OAuth2AccessTokenJsonExtractor.java:64)^[[0m^[[0m
  at 
com.github.scribejava.core.extractors.OAuth2AccessTokenJsonExtractor.extract(OAuth2AccessTokenJsonExtractor.java:37)^[[0m^[[0m
  at 
com.github.scribejava.core.extractors.OAuth2AccessTokenJsonExtractor.extract(OAuth2AccessTokenJsonExtractor.java:12)^[[0m^[[0m
  at 
com.github.scribejava.core.oauth.OAuth20Service$1.convert(OAuth20Service.java:47)^[[0m^[[0m
  at 
com.github.scribejava.core.oauth.OAuth20Service$1.convert(OAuth20Service.java:43)^[[0m^[[0m
{code}

It looks, like authorize url has moved recently. For me the following change 
worked:
-  super.authorizeUrl.replace("https://accounts.google.com;, host)
+  super.authorizeUrl.replace("https://accounts.google.com/ManageAccount;, 
host)

I didn't check the rest of the test (what responses are sent, what secured 
endpoint it tries, etc. But I don't expect much changed there.


> Oauth2 tests fail
> -
>
> Key: GEARPUMP-284
> URL: https://issues.apache.org/jira/browse/GEARPUMP-284
> Project: Apache Gearpump
>  Issue Type: Bug
>      Components: services
>Affects Versions: 0.8.2
>Reporter: Karol Brejna
>Assignee: Karol Brejna
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> Running tests show that oauth2 tests fail.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

IntelliJ IDEA licence expired

2017-05-09 Thread Karol Brejna

I've just noticed, that our IntelliJ license for Gearpump has expired.

My license details:

Licensed to: GearPump
License restriction: For non-commercial open source development only
Valid through: April 21, 2017

Do you remember how to renew the license with JetBrains?

Regards,
Karol

[jira] [Comment Edited] (GEARPUMP-284) Oauth2 tests fail

2017-05-08 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000380#comment-16000380
 ] 

Karol Brejna edited comment on GEARPUMP-284 at 5/8/17 8:51 AM:
---

[~mauzhang] Let me try to check it. I'll get back with results tomorrow.


was (Author: karol_brejna):
[~mauzhang] Let me try to fix it. I'll get back with results tomorrow.

> Oauth2 tests fail
> -
>
> Key: GEARPUMP-284
> URL: https://issues.apache.org/jira/browse/GEARPUMP-284
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.2
>Reporter: Karol Brejna
>    Assignee: Karol Brejna
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> Running tests show that oauth2 tests fail.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEARPUMP-304) add a ElasticSearch sink to integrate with gearpump

2017-05-08 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000389#comment-16000389
 ] 

Karol Brejna commented on GEARPUMP-304:
---

[~mauzhang] Yes, I had a working ElasticSearch sink and was a bit stuck with an 
example (conflicting dependencies).

[~yanghua] There is already a ticket for this: 
https://issues.apache.org/jira/browse/GEARPUMP-167
Please, hold on your work on this for a day or two. I'll dig out my latest code 
and share with you. We can discuss if we should continue with that or start 
over.
What do you think?


> add a ElasticSearch sink to integrate with gearpump
> ---
>
> Key: GEARPUMP-304
> URL: https://issues.apache.org/jira/browse/GEARPUMP-304
> Project: Apache Gearpump
>  Issue Type: Task
>  Components: connectors
>Reporter: yanghua
>Assignee: yanghua
>
> let the sinked messages could be built full-text indices.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEARPUMP-284) Oauth2 tests fail

2017-05-08 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000380#comment-16000380
 ] 

Karol Brejna commented on GEARPUMP-284:
---

[~mauzhang] Let me try to fix it. I'll get back with results tomorrow.

> Oauth2 tests fail
> -
>
> Key: GEARPUMP-284
> URL: https://issues.apache.org/jira/browse/GEARPUMP-284
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.2
>Reporter: Karol Brejna
>    Assignee: Karol Brejna
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> Running tests show that oauth2 tests fail.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: We got MessageLossException from task Some(TaskId(0,0)), replaying application...

2017-05-05 Thread Karol Brejna

Ramin,
Is there a chance for you to share the code?

What is your datasource?

Regards,
Karol

W dniu pt., 5.05.2017 o 18:06 Ramin Etemaadi 
napisał(a):

> Hi team,
>
> Thanks for your great job on Gearpump project.
>
> After upgrading from 0.8.1 to 0.8.3 (and adjusting changing interfaces), I
> got this error in the logs:
> "We got MessageLossException from task Some(TaskId(0,0)), replaying
> application..."
>
> This causes the failure of the pipeline.
>
> I searched the internet and I couldn't find any clue, can you help me with
> a indicator that what could be a stating point to debug this issue?
>
> Regards,
> Ramin
>

[GitHub] incubator-gearpump pull request #179: test

2017-05-05 Thread karol-brejna-i

GitHub user karol-brejna-i opened a pull request:

https://github.com/apache/incubator-gearpump/pull/179

test

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

 - [ ] Make sure the commit message is formatted like:
   `[GEARPUMP-] Meaningful description of pull request` 
 - [ ] Make sure tests pass via `sbt clean test`.
 - [ ] Make sure old documentation affected by the pull request has been 
updated and new documentation added for new functionality. 



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

$ git pull https://github.com/karol-brejna-i/incubator-gearpump 
GEARPUMP-297-fix-docker-links

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

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






---
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-gearpump pull request #179: test

2017-05-05 Thread karol-brejna-i

Github user karol-brejna-i closed the pull request at:

https://github.com/apache/incubator-gearpump/pull/179


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

Re: GSoC 2017 student projects announced

2017-05-05 Thread Karol Brejna

Buddhi,

Congrats and good luck!
I'll keep my fingers crossed ;-)

Regards,
Karol

On Fri, May 5, 2017 at 7:43 AM, Buddhi Ayesha Rathnayaka
 wrote:
> I am thrilled to have this great opportunity. First, I want to thank Manu
> Zhang for helping me throughout the GSoC proposal submission process. It
> was the good communication between ourselves that helped me get beyond the
> proposal submission process. I hope to continue that until I successfully
> complete this project.
>
> For everyone, I want to say Hi!
>
> I am a final year undergraduate of Computer Science & Engineering,
> University of Moratuwa, Sri Lanka. I have experience on working in
> open-source java projects. I usually spend my leisure time in innovative
> projects and present them in hackathons.
>
> Thanks & Regards,
>
> On 5 May 2017 at 06:51, Manu Zhang  wrote:
>
>> Hi All,
>>
>> The GSoC 2017 student projects have been announced.
>> Buddhi Ayesha is the student to work on our Add SQL Support
>>  project
>> and I'm the mentor.
>>
>> Congratulations, Buddhi !!!
>> I've assigned to GEARPUMP-217
>>  to you. Could you
>> introduce yourself to everyone ?
>>
>> Thanks,
>> Manu
>>
>>
>>
>
>
> --
>
> *H.K.D. Buddhi Ayesha Rathnayaka*Undergraduate BSc. Eng.(Hons.)
> Department of Computer Science & Engineering,
> University of Moratuwa.
> *Mobile: 0716943927*

[jira] [Commented] (GEARPUMP-303) add a RabbitMQ sink to integrate with gearpump

2017-05-05 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997919#comment-15997919
 ] 

Karol Brejna commented on GEARPUMP-303:
---

Oh, I see you have already prepared a PR! ;-)

Let me look at it...


> add a RabbitMQ sink to integrate with gearpump
> --
>
> Key: GEARPUMP-303
> URL: https://issues.apache.org/jira/browse/GEARPUMP-303
> Project: Apache Gearpump
>  Issue Type: Task
>Reporter: yanghua
>Assignee: yanghua
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (GEARPUMP-302) gearpump.apache.org page fix 'latest release' label

2017-04-28 Thread Karol Brejna (JIRA)

Karol Brejna created GEARPUMP-302:
-

 Summary: gearpump.apache.org page fix 'latest release' label
 Key: GEARPUMP-302
 URL: https://issues.apache.org/jira/browse/GEARPUMP-302
 Project: Apache Gearpump
  Issue Type: Bug
  Components: doc
Affects Versions: 0.8.3
Reporter: Karol Brejna
Assignee: Karol Brejna


The link is generated automatically only partly - the visibile part is ok, but 
the link leads to hardcoded version.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEARPUMP-300) java.io.NotSerializableException official DSL version for Wordcount in java

2017-04-27 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15986444#comment-15986444
 ] 

Karol Brejna commented on GEARPUMP-300:
---

[~yanghua] Actually, we are right now in a process of publishing new release 
(0.8.3) that should have the fix.

For now, you can find a binary of new version here: 
https://dist.apache.org/repos/dist/dev/incubator/gearpump/0.8.3-incubating/RC1/
(https://dist.apache.org/repos/dist/dev/incubator/gearpump/0.8.3-incubating/RC1/gearpump_2.11-0.8.3-incubating-bin.tgz)

Hopefully, very soon it will be published "officially"...

> java.io.NotSerializableException official DSL version for Wordcount in java
> ---
>
> Key: GEARPUMP-300
> URL: https://issues.apache.org/jira/browse/GEARPUMP-300
> Project: Apache Gearpump
>  Issue Type: Bug
>Reporter: yanghua
>
> java.io.NotSerializableException: java.util.ArrayList$Itr
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
>   at 
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
>   at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
>   at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>   at 
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
>   at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
>   at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>   at 
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
>   at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
>   at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>   at 
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
>   at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
>   at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>   at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
>   at 
> akka.serialization.JavaSerializer$$anonfun$toBinary$1.apply$mcV$sp(Serializer.scala:235)
>   at 
> akka.serialization.JavaSerializer$$anonfun$toBinary$1.apply(Serializer.scala:235)
>   at 
> akka.serialization.JavaSerializer$$anonfun$toBinary$1.apply(Serializer.scala:235)
>   at scala.util.DynamicVariable.withValue(DynamicVariable.scala:58)
>   at akka.serialization.JavaSerializer.toBinary(Serializer.scala:235)
>   at 
> org.apache.gearpump.cluster.UserConfig.withValue(UserConfig.scala:139)
>   at 
> org.apache.gearpump.streaming.dsl.plan.DataSourceOp.getProcessor(OP.scala:98)
>   at 
> org.apache.gearpump.streaming.dsl.plan.Planner$$anonfun$plan$2.apply(Planner.scala:50)
>   at 
> org.apache.gearpump.streaming.dsl.plan.Planner$$anonfun$plan$2.apply(Planner.scala:50)
>   at org.apache.gearpump.util.Graph$$anonfun$1.apply(Graph.scala:143)
>   at org.apache.gearpump.util.Graph$$anonfun$1.apply(Graph.scala:143)
>   at scala.collection.immutable.List.map(List.scala:277)
>   at org.apache.gearpump.util.Graph.mapVertex(Graph.scala:143)
>   at org.apache.gearpump.streaming.dsl.plan.Planner.plan(Planner.scala:50)
>   at org.apache.gearpump.streaming.dsl.StreamApp.plan(StreamApp.scala:62)
>   at 
> org.apache.gearpump.streaming.dsl.StreamApp$.streamAppToApplication(StreamApp.scala:74)
>   at 
> org.apache.gearpump.streaming.dsl.javaapi.JavaStreamApp.run(JavaStreamApp.scala:45)
>   at com.github.gearpump.demo.WordCount.main(WordCount.java:119)
>   at com.github.gearpump.demo.WordCount.main(WordCount.java:25)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.gearpump.cluster.main.AppSubmitter$.main(AppSubmitter.scala:87)
>   at 
> org.apache.gearpump.util.AkkaApp$$a

[jira] [Commented] (GEARPUMP-300) java.io.NotSerializableException official DSL version for Wordcount in java

2017-04-27 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15986097#comment-15986097
 ] 

Karol Brejna commented on GEARPUMP-300:
---

Probably something similar to https://issues.apache.org/jira/browse/GEARPUMP-247

> java.io.NotSerializableException official DSL version for Wordcount in java
> ---
>
> Key: GEARPUMP-300
> URL: https://issues.apache.org/jira/browse/GEARPUMP-300
> Project: Apache Gearpump
>  Issue Type: Bug
>Reporter: yanghua
>
> java.io.NotSerializableException: java.util.ArrayList$Itr
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
>   at 
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
>   at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
>   at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>   at 
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
>   at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
>   at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>   at 
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
>   at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
>   at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>   at 
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
>   at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
>   at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
>   at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
>   at 
> akka.serialization.JavaSerializer$$anonfun$toBinary$1.apply$mcV$sp(Serializer.scala:235)
>   at 
> akka.serialization.JavaSerializer$$anonfun$toBinary$1.apply(Serializer.scala:235)
>   at 
> akka.serialization.JavaSerializer$$anonfun$toBinary$1.apply(Serializer.scala:235)
>   at scala.util.DynamicVariable.withValue(DynamicVariable.scala:58)
>   at akka.serialization.JavaSerializer.toBinary(Serializer.scala:235)
>   at 
> org.apache.gearpump.cluster.UserConfig.withValue(UserConfig.scala:139)
>   at 
> org.apache.gearpump.streaming.dsl.plan.DataSourceOp.getProcessor(OP.scala:98)
>   at 
> org.apache.gearpump.streaming.dsl.plan.Planner$$anonfun$plan$2.apply(Planner.scala:50)
>   at 
> org.apache.gearpump.streaming.dsl.plan.Planner$$anonfun$plan$2.apply(Planner.scala:50)
>   at org.apache.gearpump.util.Graph$$anonfun$1.apply(Graph.scala:143)
>   at org.apache.gearpump.util.Graph$$anonfun$1.apply(Graph.scala:143)
>   at scala.collection.immutable.List.map(List.scala:277)
>   at org.apache.gearpump.util.Graph.mapVertex(Graph.scala:143)
>   at org.apache.gearpump.streaming.dsl.plan.Planner.plan(Planner.scala:50)
>   at org.apache.gearpump.streaming.dsl.StreamApp.plan(StreamApp.scala:62)
>   at 
> org.apache.gearpump.streaming.dsl.StreamApp$.streamAppToApplication(StreamApp.scala:74)
>   at 
> org.apache.gearpump.streaming.dsl.javaapi.JavaStreamApp.run(JavaStreamApp.scala:45)
>   at com.github.gearpump.demo.WordCount.main(WordCount.java:119)
>   at com.github.gearpump.demo.WordCount.main(WordCount.java:25)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.gearpump.cluster.main.AppSubmitter$.main(AppSubmitter.scala:87)
>   at 
> org.apache.gearpump.util.AkkaApp$$anonfun$main$1.apply(AkkaApp.scala:42)
>   at 
> org.apache.gearpump.util.AkkaApp$$anonfun$main$1.apply(AkkaApp.scala:42)
>   at scala.util.Try$.apply(Try.scala:192)
>   at org.apache.gearpump.util.AkkaApp$class.main(AkkaApp.scala:41)
>   at 
> org.apache.gearpump.cluster.main.AppSubmitter$.main(AppSubmitter.scala:28)
>   at org.apache.gearpump.cluster.main.Gear$.executeCommand(Gear.scala:40)
>   at org.apache.gearpump.cluster.main.Gear$.main(Gear.scala:59)
>   at org.apache.gearpump.cluster.main.Gear.main(Gear.scala)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (GEARPUMP-296) Update incubator logo on the website

2017-04-26 Thread Karol Brejna (JIRA)


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

Karol Brejna reassigned GEARPUMP-296:
-

Assignee: Karol Brejna

> Update incubator logo on the website
> 
>
> Key: GEARPUMP-296
> URL: https://issues.apache.org/jira/browse/GEARPUMP-296
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: website
>Reporter: Manu Zhang
>Assignee: Karol Brejna
>
> The Incubator has selected a new logo and we are requested to incorporate 
> incubating branding into our logos with the materials at 
> http://incubator.apache.org/guides/press-kit.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (GEARPUMP-299) Update gearpump.apache.org page for 0.8.3 release

2017-04-26 Thread Karol Brejna (JIRA)


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

Karol Brejna resolved GEARPUMP-299.
---
Resolution: Fixed

> Update gearpump.apache.org page for 0.8.3 release
> -
>
> Key: GEARPUMP-299
> URL: https://issues.apache.org/jira/browse/GEARPUMP-299
> Project: Apache Gearpump
>  Issue Type: Task
>  Components: doc
>Affects Versions: 0.8.3
>Reporter: Karol Brejna
>    Assignee: Karol Brejna
> Fix For: 0.8.3
>
>
> Update gearpump.apache.org page



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-gearpump pull request #175: Bump version to 0.8.4-SNAPSHOT

2017-04-19 Thread karol-brejna-i

GitHub user karol-brejna-i opened a pull request:

https://github.com/apache/incubator-gearpump/pull/175

Bump version to 0.8.4-SNAPSHOT

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

 - [ ] Make sure the commit message is formatted like:
   `[GEARPUMP-] Meaningful description of pull request` 
 - [ ] Make sure tests pass via `sbt clean test`.
 - [ ] Make sure old documentation affected by the pull request has been 
updated and new documentation added for new functionality. 



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

$ git pull https://github.com/karol-brejna-i/incubator-gearpump 
GEARPUMP-294-version-bump

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

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


commit bdb147d7921d2196b9a28e696247d62875440ef8
Author: karol brejna <karol.bre...@intel.com>
Date:   2017-04-19T11:05:09Z

Bump version to 0.8.4-SNAPSHOT




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

[RESULT][VOTE] Apache Gearpump (incubating) 0.8.3-RC1

2017-04-19 Thread Karol Brejna

Dear IPMC Community,

I am pleased to announce that the Incubator PMC has approved 0.8.3-RC1
of Apache Gearpump (Incubating) for release as version 0.8.3 (Incubating).

The vote has passed with:
- three binding "+1" votes
- no "0" votes
- no "-1" votes

The votes were 
(https://www.mail-archive.com/general@incubator.apache.org/msg59297.html):
- +1, Willem Jiang (binding)
- +1, John D. Ament (binding)
- +1, Jean-Baptiste Onofré (binding)
- +1, Wang, Gang1 (non-binding)

Thank you, for your support!

We'll continue with the release now.

Karol,
on behalf of Apache Gearpump PPMC

[VOTE][REMINDER] Apache Gearpump (incubating) 0.8.3-RC1

2017-04-14 Thread Karol Brejna

Dear IPMC Community,

Here is a kindly reminder that Apache Gearpump (incubating) 0.8.3-RC1
release vote is on.

We already have one +1 vote (thanks Gary!) and still need just a few ;-)

Regards,
Karol

On Tue, Apr 11, 2017 at 11:33 AM, Karol Brejna <karolbre...@apache.org> wrote:
> Hi IPMC Community,
>
> The PPMC vote to release Apache Gearpump (incubating) 0.8.3-RC1 has passed.
> We would like to now submit this release candidate to the IPMC.
>
> The PPMC vote thread is here:
> https://lists.apache.org/thread.html/0e1022d2f3b5b2a2b879e4c278d7fc44d094058550d47ae7e07702ec@%3Cdev.gearpump.apache.org%3E
>
> The source and binary tarballs, including signatures, digests, etc.
> can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/gearpump/0.8.3-incubating/RC1/
>
> Release artifacts are signed with the key with fingerprint:
> 3F12 81A2 DB58 0842 5ABA  6962 D8A8 4FBC 0A83 B291
>
> The KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/gearpump/KEYS
>
> The tag to be voted upon is:
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=shortlog;h=refs/tags/0.8.3-RC1
>
> The release hash is:
> https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=commit;h=80f49154428cd18b5a27d946b8c9536124849cc9
>
> For information about the contents of this release see:
> https://issues.apache.org/jira/browse/GEARPUMP-294?jql=project%20%3D%20GEARPUMP%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%200.8.3
>
> This vote will be open for 72 hours (Thursday, April 13, 2017 at 3:00AM PST).
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, run the
> binary artifacts in the binary release and test.
> Please vote:
>
> [ ] +1 Release this package as gearpump-0.8.3
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>
> Thanks,
> Karol

[jira] [Commented] (GEARPUMP-296) Update incubator logo on the website

2017-04-14 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968704#comment-15968704
 ] 

Karol Brejna commented on GEARPUMP-296:
---

We could do the change while updating docs/site after 0.8.3 release...

> Update incubator logo on the website
> 
>
> Key: GEARPUMP-296
> URL: https://issues.apache.org/jira/browse/GEARPUMP-296
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: website
>Reporter: Manu Zhang
>
> The Incubator has selected a new logo and we are requested to incorporate 
> incubating branding into our logos with the materials at 
> http://incubator.apache.org/guides/press-kit.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[VOTE] Apache Gearpump (incubating) 0.8.3-RC1

2017-04-11 Thread Karol Brejna

Hi IPMC Community,

The PPMC vote to release Apache Gearpump (incubating) 0.8.3-RC1 has passed.
We would like to now submit this release candidate to the IPMC.

The PPMC vote thread is here:
https://lists.apache.org/thread.html/0e1022d2f3b5b2a2b879e4c278d7fc44d094058550d47ae7e07702ec@%3Cdev.gearpump.apache.org%3E

The source and binary tarballs, including signatures, digests, etc.
can be found at:
https://dist.apache.org/repos/dist/dev/incubator/gearpump/0.8.3-incubating/RC1/

Release artifacts are signed with the key with fingerprint:
3F12 81A2 DB58 0842 5ABA  6962 D8A8 4FBC 0A83 B291

The KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/gearpump/KEYS

The tag to be voted upon is:
https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=shortlog;h=refs/tags/0.8.3-RC1

The release hash is:
https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=commit;h=80f49154428cd18b5a27d946b8c9536124849cc9

For information about the contents of this release see:
https://issues.apache.org/jira/browse/GEARPUMP-294?jql=project%20%3D%20GEARPUMP%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%200.8.3

This vote will be open for 72 hours (Thursday, April 13, 2017 at 3:00AM PST).

Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, run the
binary artifacts in the binary release and test.
Please vote:

[ ] +1 Release this package as gearpump-0.8.3
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

Thanks,
Karol

[VOTE] Release of Apache Gearpump 0.8.3-incubating, release candidate #1

2017-04-06 Thread Karol Brejna

Hi Gearpump Community,

This is a call for a discussion releasing Apache Gearpump
0.8.3-incubating, release candidate #1.

The source and binary tarballs, including signatures, digests, etc.
can be found at:
https://dist.apache.org/repos/dist/dev/incubator/gearpump/0.8.3-incubating/RC1/

Release artifacts are signed with the key with fingerprint:
3F12 81A2 DB58 0842 5ABA  6962 D8A8 4FBC 0A83 B291

The KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/gearpump/KEYS

The tag to be voted upon is:
https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=shortlog;h=refs/tags/0.8.3-RC1

The release hash is:
https://git-wip-us.apache.org/repos/asf?p=incubator-gearpump.git;a=commit;h=80f49154428cd18b5a27d946b8c9536124849cc9

For information about the contents of this release see:
https://issues.apache.org/jira/browse/GEARPUMP-294?jql=project%20%3D%20GEARPUMP%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%200.8.3

This vote will be open for 72 hours (Sunday, April 9, 2017 at 4:00PM PST).

Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, run the
binary artifacts in the binary release and test.
Please vote:

[ ] +1 Release this package as gearpump-0.8.2
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

Thanks,
Karol

Gearpump - SVN access

2017-03-23 Thread Karol Brejna

I am preparing next release of Apache Gearpump (incubating).

I try to commit source tarballs to SVN
(https://dist.apache.org/repos/dist/dev/incubator/gearpump')


When I do 'svn commit' I am asked for credentials that I do not know.
I've never done this before, probabably I have no account there.

Could you, please, help me with this?

Regards,
Karol

[jira] [Updated] (GEARPUMP-200) A missing gear.conf in services and other gearpump commands should result in an ERROR to the log

2017-03-17 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-200:
--
Fix Version/s: (was: 0.8.3)

> A missing gear.conf in services and other gearpump commands should result in 
> an ERROR to the log
> 
>
> Key: GEARPUMP-200
> URL: https://issues.apache.org/jira/browse/GEARPUMP-200
> Project: Apache Gearpump
>  Issue Type: Bug
>Affects Versions: 0.8.1
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
>
> Commands like services, master, local, etc are built with Config logic that 
> uses gear.conf with fallback to geardefault.conf. If gear.conf is missing 
> from the classpath of these commands we should issue a WARNING or ERROR and 
> treat it not unlike a missing jar file since it is a critical dependency.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEARPUMP-223) Support Redis Cluster Sink

2017-03-17 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-223:
--
Fix Version/s: (was: 0.8.3)

> Support Redis Cluster Sink
> --
>
> Key: GEARPUMP-223
> URL: https://issues.apache.org/jira/browse/GEARPUMP-223
> Project: Apache Gearpump
>  Issue Type: Sub-task
>Reporter: darion yaphet
>Assignee: darion yaphet
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEARPUMP-199) high throughput results in high GC costs

2017-03-17 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-199:
--
Fix Version/s: (was: 0.8.3)

> high throughput results in high GC costs
> 
>
> Key: GEARPUMP-199
> URL: https://issues.apache.org/jira/browse/GEARPUMP-199
> Project: Apache Gearpump
>  Issue Type: Improvement
>Affects Versions: 0.8.1
>Reporter: Kam Kasravi
>Assignee: Manu Zhang
> Attachments: Pasted image at 2016_08_31 01_50 AM.png
>
>
> we should look to minimize GC costs - perhaps following what paypal squbs did 
> with persistentbuffer (also would be able to integrate with akka-streams)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEARPUMP-206) access to upstream and downstream processors

2017-03-17 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-206:
--
Fix Version/s: (was: 0.8.3)
   0.8.4

> access to upstream and downstream processors
> 
>
> Key: GEARPUMP-206
> URL: https://issues.apache.org/jira/browse/GEARPUMP-206
> Project: Apache Gearpump
>  Issue Type: Sub-task
>Affects Versions: 0.8.1
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
> Fix For: 0.8.4
>
>
> akka-streams requires the ability to access both upstream and downstream 
> processors. For upstream akka-streams will pull - we need to emulate 
> something similar



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEARPUMP-193) Need ability to request upstream messages (pull)

2017-03-17 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-193:
--
Fix Version/s: (was: 0.8.3)

> Need ability to request upstream messages (pull)
> 
>
> Key: GEARPUMP-193
> URL: https://issues.apache.org/jira/browse/GEARPUMP-193
> Project: Apache Gearpump
>  Issue Type: Sub-task
>Affects Versions: 0.8.1
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
> Fix For: 0.8.4
>
>
> akka-streams Interleave GraphStage will iterate through upstream processors 
> pulling a certain number of messages for each. We do not have this ability.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEARPUMP-191) add ability to control rate to TaskActor

2017-03-17 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-191:
--
Fix Version/s: (was: 0.8.3)
   0.8.4

> add ability to control rate to TaskActor
> 
>
> Key: GEARPUMP-191
> URL: https://issues.apache.org/jira/browse/GEARPUMP-191
> Project: Apache Gearpump
>  Issue Type: Sub-task
>Affects Versions: 0.8.1
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
> Fix For: 0.8.4
>
>
> akka-streams requires an ability to control the rate of input and output of 
> messages within a task. See Throttle 
> (http://doc.akka.io/docs/akka/current/scala/stream/stream-quickstart.html#Time-Based_Processing)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEARPUMP-190) Add logo with text to site

2017-03-17 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-190:
--
Fix Version/s: (was: 0.8.3)
   0.8.4

> Add logo with text to site
> --
>
> Key: GEARPUMP-190
> URL: https://issues.apache.org/jira/browse/GEARPUMP-190
> Project: Apache Gearpump
>  Issue Type: Task
>Affects Versions: 0.8.1
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
>Priority: Minor
> Fix For: 0.8.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEARPUMP-22) Support akka-streams Gearpump Materializer

2017-03-17 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-22:
-
Fix Version/s: (was: 0.8.3)
   0.8.4

> Support akka-streams Gearpump Materializer
> --
>
> Key: GEARPUMP-22
> URL: https://issues.apache.org/jira/browse/GEARPUMP-22
> Project: Apache Gearpump
>  Issue Type: New Feature
>  Components: akkastream
>Affects Versions: 0.8.0
>Reporter: Kam Kasravi
>Assignee: Kam Kasravi
> Fix For: 0.8.4
>
>
> Reenable experiments/akkastream to work with akka 2.4.3 (latest on master)
> Create PR's for akka team related to changes required for Gearpump 
> Materializer



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEARPUMP-252) return application status to client

2017-03-15 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-252:
--
Fix Version/s: 0.8.3

> return application status to client
> ---
>
> Key: GEARPUMP-252
> URL: https://issues.apache.org/jira/browse/GEARPUMP-252
> Project: Apache Gearpump
>  Issue Type: Improvement
>Affects Versions: 0.8.2
>Reporter: Manu Zhang
>Assignee: Huafeng Wang
> Fix For: 0.8.3
>
>
> Currently, client exits after submitting applications and has no idea of the 
> application status. It will be valuable to return such information to client. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (GEARPUMP-267) Kafka integration test failure due to docker-kafka version incompatibility

2017-03-15 Thread Karol Brejna (JIRA)


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

Karol Brejna resolved GEARPUMP-267.
---
Resolution: Duplicate

> Kafka integration test failure due to docker-kafka version incompatibility
> --
>
> Key: GEARPUMP-267
> URL: https://issues.apache.org/jira/browse/GEARPUMP-267
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: integrationtest
>Reporter: Manu Zhang
>Assignee: Karol Brejna
>
> The current "spotify/kafka" has been updated to kafka 0.10 while Gearpump 
> depends on kafka 0.8, and the author doesn't provide history tags.  There is 
> an open [issue|https://github.com/spotify/docker-kafka/issues/61] but the 
> repo doesn't seem to be under active development. An alternative is 
> https://github.com/wurstmeister/kafka-docker



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (GEARPUMP-281) Put dockerfiles used in interation test into integrationtest/docker

2017-03-15 Thread Karol Brejna (JIRA)


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

Karol Brejna resolved GEARPUMP-281.
---
Resolution: Fixed

> Put dockerfiles used in interation test into integrationtest/docker
> ---
>
> Key: GEARPUMP-281
> URL: https://issues.apache.org/jira/browse/GEARPUMP-281
> Project: Apache Gearpump
>  Issue Type: Task
>  Components: integrationtest
> Environment: N/A
>Reporter: Karol Brejna
>    Assignee: Karol Brejna
>Priority: Minor
> Fix For: 0.8.3
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEARPUMP-255) application id is not returned to user in Java Stream DSL

2017-03-15 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-255:
--
Fix Version/s: 0.8.3

> application id is not returned to user in Java Stream DSL
> -
>
> Key: GEARPUMP-255
> URL: https://issues.apache.org/jira/browse/GEARPUMP-255
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: streaming
>Affects Versions: 0.8.2
>Reporter: Manu Zhang
>Assignee: Manu Zhang
> Fix For: 0.8.3
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEARPUMP-265) remove AppMasterRuntimeInfo from AppMasterContext

2017-03-15 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-265:
--
Fix Version/s: 0.8.3

> remove AppMasterRuntimeInfo from AppMasterContext
> -
>
> Key: GEARPUMP-265
> URL: https://issues.apache.org/jira/browse/GEARPUMP-265
> Project: Apache Gearpump
>  Issue Type: Sub-task
>Affects Versions: 0.8.2
>Reporter: Huafeng Wang
>Assignee: Huafeng Wang
> Fix For: 0.8.3
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEARPUMP-264) refactor Application status implementation

2017-03-15 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-264:
--
Fix Version/s: 0.8.3

> refactor Application status implementation
> --
>
> Key: GEARPUMP-264
> URL: https://issues.apache.org/jira/browse/GEARPUMP-264
> Project: Apache Gearpump
>  Issue Type: Sub-task
>Reporter: Huafeng Wang
>Assignee: Huafeng Wang
> Fix For: 0.8.3
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-gearpump pull request #162: [GEARPUMP-281] Using new version of do...

2017-02-28 Thread karol-brejna-i

Github user karol-brejna-i commented on a diff in the pull request:

https://github.com/apache/incubator-gearpump/pull/162#discussion_r103432682
  
--- Diff: integrationtest/docker/java/README.md ---
@@ -0,0 +1,18 @@
+A minimalistic Oracle JDK 8 container on top of busybox.
+
+We used to base Gearpump Cluster Launcher on errordeveloper/oracle-jre 
image but it stuck on version 8u66-b17 and doesn't support tagging.
+We also probably hit a Java bug 
(http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8133205) that requires 
never version of JRE.
--- End diff --

fixed


---
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-gearpump pull request #158: [GEARPUMP-267] Changing docker image f...

2017-02-28 Thread karol-brejna-i

Github user karol-brejna-i closed the pull request at:

https://github.com/apache/incubator-gearpump/pull/158


---
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-gearpump pull request #162: [GEARPUMP-281] Using new version of do...

2017-02-28 Thread karol-brejna-i

Github user karol-brejna-i commented on a diff in the pull request:

https://github.com/apache/incubator-gearpump/pull/162#discussion_r103432537
  
--- Diff: integrationtest/docker/kafka/README.md ---
@@ -0,0 +1,89 @@
+Kafka in Docker
+===
+
+**This is a fork spotify/kafka image. We decided to make it, because the 
project does not maintain proper tagging. 
+For now our tests focus on Kafka 0.8.x, so here is a version that supports 
Kafka 0.8.x.
+For latest version of kafka image go to the original project.**
+   
+This repository provides everything you need to run Kafka in Docker.
+
+For convenience also contains a packaged proxy that can be used to get 
data from
+a legacy Kafka 7 cluster into a dockerized Kafka 8.
+
+Why?
+---
+The main hurdle of running Kafka in Docker is that it depends on Zookeeper.
+Compared to other Kafka docker images, this one runs both Zookeeper and 
Kafka
+in the same container. This means:
+
+* No dependency on an external Zookeeper host, or linking to another 
container
+* Zookeeper and Kafka are configured to work together out of the box
+
+Run
+---
+
+```bash
+docker run -p 2181:2181 -p 9092:9092 --env ADVERTISED_HOST=`docker-machine 
ip \`docker-machine active\`` --env ADVERTISED_PORT=9092 grubykarol/kafka
--- End diff --

No, we use it without it. It's just example from original README.


---
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-gearpump issue #158: [GEARPUMP-267] Changing docker image for Kafk...

2017-02-28 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/158
  
Now it's obsolete (implemented by two other PRs). Closing.


---
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] (GEARPUMP-284) Oauth2 tests fail

2017-02-27 Thread Karol Brejna (JIRA)

Karol Brejna created GEARPUMP-284:
-

 Summary: Oauth2 tests fail
 Key: GEARPUMP-284
 URL: https://issues.apache.org/jira/browse/GEARPUMP-284
 Project: Apache Gearpump
  Issue Type: Bug
  Components: services
Affects Versions: 0.8.2
Reporter: Karol Brejna
Assignee: Karol Brejna


Running tests show that oauth2 tests fail.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-gearpump issue #158: [GEARPUMP-267] Changing docker image for Kafk...

2017-02-24 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/158
  
I used Java 8 from Oracle, more precisely:
``` java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
```
Let me upgrade to newer version and send an update.



---
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] (GEARPUMP-281) Put dockerfiles used in interation test into integrationtest/docker

2017-02-23 Thread Karol Brejna (JIRA)

Karol Brejna created GEARPUMP-281:
-

 Summary: Put dockerfiles used in interation test into 
integrationtest/docker
 Key: GEARPUMP-281
 URL: https://issues.apache.org/jira/browse/GEARPUMP-281
 Project: Apache Gearpump
  Issue Type: Task
  Components: integrationtest
 Environment: N/A
Reporter: Karol Brejna
Priority: Minor
 Fix For: 0.8.3






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (GEARPUMP-236) java.lang.VerifyError after assembly gearpump-core

2017-02-23 Thread Karol Brejna (JIRA)


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

Karol Brejna resolved GEARPUMP-236.
---
   Resolution: Fixed
Fix Version/s: 0.8.3

> java.lang.VerifyError after assembly gearpump-core
> --
>
> Key: GEARPUMP-236
> URL: https://issues.apache.org/jira/browse/GEARPUMP-236
> Project: Apache Gearpump
>  Issue Type: Bug
>Reporter: Manu Zhang
>    Assignee: Karol Brejna
> Fix For: 0.8.3
>
>
> {{java.lang.VerifyError}} exceptions are thrown in all main processes 
> (master, worker, executor, etc) after we assembly {{gearpump-core}}.  I added 
> {{-noverify}} to all of their jvm options as a work-around. We should find 
> the root cause and remove it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (GEARPUMP-112) DAG chart in dashboard does not show data, when flow is small

2017-02-23 Thread Karol Brejna (JIRA)


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

Karol Brejna closed GEARPUMP-112.
-

> DAG chart in dashboard does not show data, when flow is small
> -
>
> Key: GEARPUMP-112
> URL: https://issues.apache.org/jira/browse/GEARPUMP-112
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.0
>Reporter: Piotr Grabuszynski
>    Assignee: Karol Brejna
> Fix For: 0.8.3
>
> Attachments: gp-flow.jpg, gp-screen-2.jpg, gp-screen-metrics.jpg, 
> gp-screen-overview.jpg, metrics_last.png, overview_last.png
>
>
> BUG:
> After deploying application on Apache Gearpump, DAG chart and data near it, 
> shows always the same value, and lines and nodes on chart doesn't grow if the 
> flow is about 3 requests / second.
> WAY TO REPRODUCE:
> 1. Deploy application on Apache Gearpump.
> 2. To input kafka topic send ~3 requests/sec.
> 3. Go to dashboard, choose your app and go to DAG tab.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEARPUMP-112) DAG chart in dashboard does not show data, when flow is small

2017-02-23 Thread Karol Brejna (JIRA)


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

Karol Brejna updated GEARPUMP-112:
--
Attachment: overview_last.png
metrics_last.png

> DAG chart in dashboard does not show data, when flow is small
> -
>
> Key: GEARPUMP-112
> URL: https://issues.apache.org/jira/browse/GEARPUMP-112
> Project: Apache Gearpump
>  Issue Type: Bug
>  Components: services
>Affects Versions: 0.8.0
>Reporter: Piotr Grabuszynski
>    Assignee: Karol Brejna
> Fix For: 0.8.3
>
> Attachments: gp-flow.jpg, gp-screen-2.jpg, gp-screen-metrics.jpg, 
> gp-screen-overview.jpg, metrics_last.png, overview_last.png
>
>
> BUG:
> After deploying application on Apache Gearpump, DAG chart and data near it, 
> shows always the same value, and lines and nodes on chart doesn't grow if the 
> flow is about 3 requests / second.
> WAY TO REPRODUCE:
> 1. Deploy application on Apache Gearpump.
> 2. To input kafka topic send ~3 requests/sec.
> 3. Go to dashboard, choose your app and go to DAG tab.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEARPUMP-125) Kafka New Consumer

2017-02-23 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880331#comment-15880331
 ] 

Karol Brejna commented on GEARPUMP-125:
---

Actually, it looks like it's duplicated by 
https://issues.apache.org/jira/browse/GEARPUMP-220 (152 concerns STORM upgrade).
Still, I think we could close this one.

> Kafka New Consumer
> --
>
> Key: GEARPUMP-125
> URL: https://issues.apache.org/jira/browse/GEARPUMP-125
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: kafka
>Affects Versions: 0.8.0
>Reporter: darion yaphet
>Assignee: darion yaphet
>
> Kafka 0.9 have released about half a year . In this new version it's include 
> a new redesigned consumer which is don't dependency on ZooKeeper and support 
> security features (authenticate and permissions )  . 
> [Apache Kafka 0.9 is 
> Released|http://www.confluent.io/blog/apache-kafka-0.9-is-released]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (GEARPUMP-158) Docker/kubernetes deployment PoC

2017-02-23 Thread Karol Brejna (JIRA)


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

Karol Brejna reassigned GEARPUMP-158:
-

Assignee: Karol Brejna

> Docker/kubernetes deployment PoC
> 
>
> Key: GEARPUMP-158
> URL: https://issues.apache.org/jira/browse/GEARPUMP-158
> Project: Apache Gearpump
>  Issue Type: Task
>        Reporter: Karol Brejna
>    Assignee: Karol Brejna
>
> Kubernetes is an open-source system for automating deployment, scaling, and 
> management of containerized applications.
> We already use docker for integration test (some restrictions apply, for 
> example - a single master cluster)
> This should give us a good start to having "full" docker/kubernetes support 
> (HA).
> After this PoC we should have at least:
> * dockerfiles for masters and workers
> * kubernetes descriptors that enable deploying a cluster
> In the future we could think about k8s-aware workers that could spawn new 
> executors using kubernetes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEARPUMP-192) refactor example sources task to use DataSource API

2017-02-23 Thread Karol Brejna (JIRA)


[ 
https://issues.apache.org/jira/browse/GEARPUMP-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880325#comment-15880325
 ] 

Karol Brejna commented on GEARPUMP-192:
---

It looks like we could close the issue. The PR has been merged.

> refactor example sources task to use DataSource API
> ---
>
> Key: GEARPUMP-192
> URL: https://issues.apache.org/jira/browse/GEARPUMP-192
> Project: Apache Gearpump
>  Issue Type: Improvement
>  Components: streaming
>Affects Versions: 0.8.1
>Reporter: Manu Zhang
>Assignee: Kaifang Bao
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (GEARPUMP-253) Yarn-client fail while launching

2017-02-23 Thread Karol Brejna (JIRA)


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

Karol Brejna reassigned GEARPUMP-253:
-

Assignee: Karol Brejna

> Yarn-client fail while launching
> 
>
> Key: GEARPUMP-253
> URL: https://issues.apache.org/jira/browse/GEARPUMP-253
> Project: Apache Gearpump
>  Issue Type: Bug
>Reporter: Piotr Grabuszynski
>    Assignee: Karol Brejna
>Priority: Minor
>
> I tried to spawn Gearpump on Yarn. First, all yarn-config files has been 
> copied to conf/yarnconf and Gearpump has been stored in HDFS under path 
> /usr/lib/gearpump/gearpump-2.11-0.8.3-SNAPSHOT.zip. Then, I called command: 
> bin/yarnclient launch -package 
> /usr/lib/gearpump/gearpump-2.11-0.8.3-SNAPSHOT.zip and got following error:
> {code}
> [ClusterConfig$] loading config file application.conf...
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> com/google/common/base/Preconditions
> at 
> org.apache.hadoop.conf.Configuration$DeprecationDelta.(Configuration.java:318)
> at 
> org.apache.hadoop.conf.Configuration$DeprecationDelta.(Configuration.java:331)
> at 
> org.apache.hadoop.conf.Configuration.(Configuration.java:413)
> at 
> org.apache.gearpump.experiments.yarn.glue.YarnConfig$.$lessinit$greater$default$1(YarnConfig.scala:27)
> at 
> org.apache.gearpump.experiments.yarn.client.LaunchCluster$.main(LaunchCluster.scala:193)
> at 
> org.apache.gearpump.util.AkkaApp$$anonfun$main$1.apply(AkkaApp.scala:42)
> at 
> org.apache.gearpump.util.AkkaApp$$anonfun$main$1.apply(AkkaApp.scala:42)
> at scala.util.Try$.apply(Try.scala:192)
> at org.apache.gearpump.util.AkkaApp$class.main(AkkaApp.scala:41)
> at 
> org.apache.gearpump.experiments.yarn.client.LaunchCluster$.main(LaunchCluster.scala:160)
> at 
> org.apache.gearpump.experiments.yarn.client.Client$.main(Client.scala:49)
> at 
> org.apache.gearpump.experiments.yarn.client.Client.main(Client.scala)
> Caused by: java.lang.ClassNotFoundException: 
> com.google.common.base.Preconditions
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 12 more
> {code}
> commit used to build package: 1bf6a9ba8fa774b985fcd90a5d6bef129a4fb9a5



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (GEARPUMP-253) Yarn-client fail while launching

2017-02-23 Thread Karol Brejna (JIRA)


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

Karol Brejna resolved GEARPUMP-253.
---
   Resolution: Fixed
Fix Version/s: 0.8.3

> Yarn-client fail while launching
> 
>
> Key: GEARPUMP-253
> URL: https://issues.apache.org/jira/browse/GEARPUMP-253
> Project: Apache Gearpump
>  Issue Type: Bug
>Reporter: Piotr Grabuszynski
>    Assignee: Karol Brejna
>Priority: Minor
> Fix For: 0.8.3
>
>
> I tried to spawn Gearpump on Yarn. First, all yarn-config files has been 
> copied to conf/yarnconf and Gearpump has been stored in HDFS under path 
> /usr/lib/gearpump/gearpump-2.11-0.8.3-SNAPSHOT.zip. Then, I called command: 
> bin/yarnclient launch -package 
> /usr/lib/gearpump/gearpump-2.11-0.8.3-SNAPSHOT.zip and got following error:
> {code}
> [ClusterConfig$] loading config file application.conf...
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> com/google/common/base/Preconditions
> at 
> org.apache.hadoop.conf.Configuration$DeprecationDelta.(Configuration.java:318)
> at 
> org.apache.hadoop.conf.Configuration$DeprecationDelta.(Configuration.java:331)
> at 
> org.apache.hadoop.conf.Configuration.(Configuration.java:413)
> at 
> org.apache.gearpump.experiments.yarn.glue.YarnConfig$.$lessinit$greater$default$1(YarnConfig.scala:27)
> at 
> org.apache.gearpump.experiments.yarn.client.LaunchCluster$.main(LaunchCluster.scala:193)
> at 
> org.apache.gearpump.util.AkkaApp$$anonfun$main$1.apply(AkkaApp.scala:42)
> at 
> org.apache.gearpump.util.AkkaApp$$anonfun$main$1.apply(AkkaApp.scala:42)
> at scala.util.Try$.apply(Try.scala:192)
> at org.apache.gearpump.util.AkkaApp$class.main(AkkaApp.scala:41)
> at 
> org.apache.gearpump.experiments.yarn.client.LaunchCluster$.main(LaunchCluster.scala:160)
> at 
> org.apache.gearpump.experiments.yarn.client.Client$.main(Client.scala:49)
> at 
> org.apache.gearpump.experiments.yarn.client.Client.main(Client.scala)
> Caused by: java.lang.ClassNotFoundException: 
> com.google.common.base.Preconditions
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 12 more
> {code}
> commit used to build package: 1bf6a9ba8fa774b985fcd90a5d6bef129a4fb9a5



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-gearpump issue #158: [GEARPUMP-267] Changing docker image for Kafk...

2017-02-22 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/158
  
Probably related to 

https://docs.oracle.com/javase/8/docs/api/java/time/Instant.html#toEpochMilli--

The logs show:
`[INFO] [02/22/2017 10:25:34.395] [KafkaSource] KafkaSource opened at start 
time -292275055-05-16T16:47:04.192Z`
Then it looks like converting it in AbstractKafkaSource.open() fails:
`maybeRecover(startTime.toEpochMilli)`


---
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-gearpump issue #158: [GEARPUMP-267] Changing docker image for Kafk...

2017-02-22 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/158
  
On the other hand converting fron tihs date works on my dev machine:
```
import java.time.Instant
type TimeStamp = Long
val MIN_TIME_MILLIS: Long = Long.MinValue
var _minClock: TimeStamp = MIN_TIME_MILLIS
val startTime = Instant.ofEpochMilli(_minClock)
val result = startTime.toEpochMilli
```


---
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-gearpump issue #158: [GEARPUMP-267] Changing docker image for Kafk...

2017-02-22 Thread karol-brejna-i

Github user karol-brejna-i commented on the issue:

https://github.com/apache/incubator-gearpump/pull/158
  
The good news is, Kafka "cluster" is up again (during integration tests).
The bad news, there is some error running Kafka example.
I found this in application logs:
```
INFO] [02/22/2017 08:20:08.282] [Executor@app2exec1] Executor received 
restart tasks
[WARN] [02/22/2017 08:20:08.282] [ProducerConfig] The configuration 
value.serializer = class 
org.apache.kafka.common.serialization.ByteArraySerializer was supplied but 
isn't a known config.
[WARN] [02/22/2017 08:20:08.283] [ProducerConfig] The configuration 
key.serializer = class 
org.apache.kafka.common.serialization.ByteArraySerializer was supplied but 
isn't a known config.
[INFO] [02/22/2017 08:20:08.283] [KafkaSource] created checkpoint store for 
[topic3,0]
[ERROR] [02/22/2017 08:20:08.283] [Executor@app2exec1] We got 
java.lang.ArithmeticException from Some(TaskId(0,0)), we will treat it as 
MessageLoss, so that the system will replay all lost message
java.lang.ArithmeticException: long overflow
at java.lang.Math.multiplyExact(Math.java:892)
at java.time.Instant.toEpochMilli(Instant.java:1232)
at 
org.apache.gearpump.streaming.kafka.lib.source.AbstractKafkaSource.open(AbstractKafkaSource.scala:94)
at 
org.apache.gearpump.streaming.source.DataSourceTask.onStart(DataSourceTask.scala:71)
at 
org.apache.gearpump.streaming.task.TaskWrapper.onStart(TaskWrapper.scala:96)
at 
org.apache.gearpump.streaming.task.TaskActor.onStart(TaskActor.scala:107)
at 
org.apache.gearpump.streaming.task.TaskActor.org$apache$gearpump$streaming$task$TaskActor$$onStartClock(TaskActor.scala:195)
at 
org.apache.gearpump.streaming.task.TaskActor$$anonfun$waitForStartClock$1.applyOrElse(TaskActor.scala:212)
at akka.actor.Actor$class.aroundReceive(Actor.scala:496)
at 
org.apache.gearpump.streaming.task.TaskActor.aroundReceive(TaskActor.scala:42)
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:526)
at akka.actor.ActorCell.invoke(ActorCell.scala:495)
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:257)
at akka.dispatch.Mailbox.run(Mailbox.scala:224)
at akka.dispatch.Mailbox.exec(Mailbox.scala:234)
at 
scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at 
scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at 
scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at 
scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
[WARN] [02/22/2017 08:20:08.284] [OneForOneStrategy] long overflow
[INFO] [02/22/2017 08:20:08.285] [DataSourceTask@app2exec1TaskId(0,0)] 
closing data source...
[INFO] [02/22/2017 08:20:08.283] [DataSinkTask@app2exec1TaskId(1,0)] 
closing data sink...
```



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

1 2 >

1 - 100 of 168 matches

Mail list logo