: dev@flink.apache.org
Subject: Re: Buffer re-ordering problem
Thanks for helping us debug this.
You can start many taskmanagers in one JVM, by using the LocalMiniCluster.
Have a look at this (manually triggered) test, which runs 100 TaskManagers in
one JVM:
https://github.com/apache/flink/blob/m
> Sent: Mittwoch, 3. Juni 2015 20:14
> To: dev@flink.apache.org
> Subject: Re: Buffer re-ordering problem
>
> Hi Sebastian!
>
> The first error that you report looks could also be a lost buffer, rather
> than a reordering.
> The second error that you post seems a serializat
Behalf Of Stephan
Ewen
Sent: Mittwoch, 3. Juni 2015 20:14
To: dev@flink.apache.org
Subject: Re: Buffer re-ordering problem
Hi Sebastian!
The first error that you report looks could also be a lost buffer, rather than
a reordering.
The second error that you post seems a serialization issue.
Both
dDeserializer.java:133)
> > at
> >
> org.apache.flink.runtime.io.network.api.reader.AbstractRecordReader.getNextRecord(AbstractRecordReader.java:64)
> > at
> >
> org.apache.flink.runtime.io.network.api.reader.MutableRecordReader.next(MutableRecordReader.java:34)
&
t(ReaderIterator.java:59)
> at
> org.apache.flink.runtime.operators.sort.UnilateralSortMerger$ReadingThread.go(UnilateralSortMerger.java:1020)
> at
> org.apache.flink.runtime.operators.sort.UnilateralSortMerger$ThreadBase.run(UnilateralSortMerger.java:781)
>
>
> -Original Mess
.@apache.org]
Sent: Mittwoch, 3. Juni 2015 10:33
To: dev@flink.apache.org
Subject: Re: Buffer re-ordering problem
This is a critical bug.
- which version are you using? If snapshot, which commit?
- what is your setup? Number of machines, datset etc?
- is it reproducible?
On Wednesday, June 3, 2015, Kru
This is a critical bug.
- which version are you using? If snapshot, which commit?
- what is your setup? Number of machines, datset etc?
- is it reproducible?
On Wednesday, June 3, 2015, Kruse, Sebastian wrote:
> Hi everyone,
>
> I had some jobs running over the night and in two of them after ab
