Yes, the issue I mentioned is solved in the next release. On Tue, May 5, 2015 at 12:56 AM, Flavio Pompermaier <pomperma...@okkam.it> wrote:
> Thanks for the support! so this issue will be solved in the next 0.9 > release? > > On Tue, May 5, 2015 at 12:17 AM, Stephan Ewen <se...@apache.org> wrote: > >> Here is a list of all values you can set: >> http://ci.apache.org/projects/flink/flink-docs-master/setup/config.html >> >> On Tue, May 5, 2015 at 12:17 AM, Stephan Ewen <se...@apache.org> wrote: >> >>> Hi Flavio! >>> >>> This may be a known and fixed issue. It relates to the fact that task >>> deployment may take long in case of big jar files. The current master >>> should not have this issue any more, but 0.9-SNAPSHOT has it. >>> >>> As a temporary workaround, you can increase "akka.ask.timeout"in the >>> flink configuration file. a value os "200 s" for example increases it to >>> 200 seconds. >>> >>> Greetings, >>> Stephan >>> >>> >>> On Mon, May 4, 2015 at 11:52 PM, Flavio Pompermaier < >>> pomperma...@okkam.it> wrote: >>> >>>> Hi to all, >>>> >>>> In my current (local) job I receive a lot of Akka timeout errors during >>>> task deploy at: >>>> >>>> >>>> org.apache.flink.runtime.executiongraph.Execution$2.onComplete(Execution.java:342) >>>> >>>> is it normal? Which parameter do I have to increase? >>>> >>>> Best, >>>> Flavio >>>> >>> >>> >> > >
