@Till: Yes I’m running the job on cloud-11 or better to say I’m using the yarn cluster and the flink-yarn package. I’m using flink-0.9-SNAPSHOT from the following commit [1] together with Timos patch [2]. I’ll send you a separate email with instructions where you can find the jars on cloud-11.
Thanks, Christoph [1] https://github.com/apache/flink/commit/06b2acf7946efc03760cacf464cead5ec2d8daa6 [2] https://github.com/apache/flink/pull/342 On 29 Jan 2015, at 09:14, Till Rohrmann <trohrm...@apache.org> wrote: > Yes actually the timeouts should not really matter. However, an exception > in the InputSplitAssigner should happen in the actor thread and thus cause > the actor to stop. This should be logged by the supervisor. > > I just checked and the method InputSplitAssigner.getNextInputSplit is not > supposed to throw any checked exceptions. > > On Thu, Jan 29, 2015 at 6:38 AM, Stephan Ewen <se...@apache.org> wrote: > >> @Till: The default timeouts are high enough that such a timeout should >> actually not occur, right? Increasing the timeouts cannot really be the >> issue. >> >> Might it be something different? What happens if there is an error in the >> code that produces the input split? Is that properly handled, or is the >> receiver simply not ever getting an answer. Could that be what happened? >>
