Re: Submission Problem

2016-03-31 Thread Till Rohrmann
The PR Ufuk referenced should fix the problem. It is a known issue. It's not merged yet, because I wanted to add an improved test case. In the documentation for version 1.1-Snapshot, I've already addressed the problem with the configuration parameter description. Cheers, Till On Mar 31, 2016 6:09

Re: Submission Problem

2016-03-31 Thread Stephan Ewen
I guess the fix is to put the entire ExecutionConfig into a "SerializedValue"? On Thu, Mar 31, 2016 at 5:34 PM, Matthias J. Sax wrote: > StormConfig is set a a global job parameter > > FlinkClient.java line 337ff > > > ExecutionConfig flinkConfig = > topology.getExecutionEnvironment().getConfig(

Re: Submission Problem

2016-03-31 Thread Matthias J. Sax
StormConfig is set a a global job parameter FlinkClient.java line 337ff > ExecutionConfig flinkConfig = topology.getExecutionEnvironment().getConfig(); > flinkConfig.setGlobalJobParameters(new StormConfig(conf)); On 03/31/2016 05:05 PM, Stephan Ewen wrote: > Hmm, it is wrong that the JobManage

Re: Submission Problem

2016-03-31 Thread Ufuk Celebi
@Till: Isn't this an instance of the bug fixed in https://github.com/apache/flink/pull/1818? On Thu, Mar 31, 2016 at 5:05 PM, Stephan Ewen wrote: > Hmm, it is wrong that the JobManager tries to load that class directly from > the actor message. > All user code should be deserialized lazily. > > H

Re: Submission Problem

2016-03-31 Thread Stephan Ewen
Hmm, it is wrong that the JobManager tries to load that class directly from the actor message. All user code should be deserialized lazily. How is that class passed? Implicitly through some config? On Thu, Mar 31, 2016 at 4:51 PM, Matthias J. Sax wrote: > Here we go... > > StormConfig.class is

Re: Submission Problem

2016-03-31 Thread Matthias J. Sax
Here we go... StormConfig.class is contained in the user jar file. I guess I need to "register" it somehow? Or is it a class loading issue? > 2016-03-31 16:47:33,095 ERROR akka.remote.EndpointWriter > - AssociationError [akka.tcp://flink@127.0.0.1:6123] <- >

Re: Submission Problem

2016-03-31 Thread Till Rohrmann
Could you please rerun the whole job with debug log level and logging of Akka's lifecycle events turned on? Cheers, Till On Thu, Mar 31, 2016 at 4:21 PM, Matthias J. Sax wrote: > enclosed the logs.. maybe you can make some sense out if them. > > On 03/31/2016 02:52 PM, Till Rohrmann wrote: > >

Re: Submission Problem

2016-03-31 Thread Matthias J. Sax
enclosed the logs.. maybe you can make some sense out if them. On 03/31/2016 02:52 PM, Till Rohrmann wrote: > I would assume that something went wrong on the JobManager side. Could you > check the logs if they contain something suspicious? Additionally you could > turn on lifecycle event logging​

Re: Submission Problem

2016-03-31 Thread Till Rohrmann
I would assume that something went wrong on the JobManager side. Could you check the logs if they contain something suspicious? Additionally you could turn on lifecycle event logging​ for Akka. Cheers, Till ​

Submission Problem

2016-03-31 Thread Matthias J. Sax
Hi, I just tried to submit Flink's Storm-Topology example via command line: bin/flink run ~/workspace_flink/flink/flink-contrib/flink-storm-examples/target/WordCount-StormTopology.jar However, I get a timeout and the program is not submitted. I tracked the problem down to the following statemen