Re: "No more bytes left" at deserialization

2016-04-27 Thread Till Rohrmann
Hi Timur, could you try to exclude the older kryo dependency from twitter.carbonite via com.twitter carbonite 1.4.0 kryo com.esotericsoftware.kryo and try whether this solves your problem. If your problem should still persist, cou

Re: "No more bytes left" at deserialization

2016-04-26 Thread Timur Fayruzov
Hi Ken, Good point actually, thanks for pointing this out. In Flink project I see that there is dependency on 2.24 and then I see transitive dependencies through twitter.carbonite has a dependency on 2.21. Also, twitter.chill that is used to manipulate Kryo as far as I understand, shows up with ve

Re: "No more bytes left" at deserialization

2016-04-26 Thread Ken Krugler
I don’t know if this is helpful, but I’d run into a similar issue (array index out of bounds during Kryo deserialization) due to having a different version of Kryo on the classpath. — Ken > On Apr 26, 2016, at 6:23pm, Timur Fayruzov wrote: > > I built master with scala 2.11 and hadoop 2.7.1,

Re: "No more bytes left" at deserialization

2016-04-26 Thread Timur Fayruzov
I built master with scala 2.11 and hadoop 2.7.1, now get a different exception (still serialization-related though): java.lang.Exception: The data preparation for task 'CHAIN CoGroup (CoGroup at com.whitepages.data.flink.FaithResolution$.pipeline(FaithResolution.scala:162)) -> Filter (Filter at co

Re: "No more bytes left" at deserialization

2016-04-26 Thread Till Rohrmann
Then let's keep finger crossed that we've found the culprit :-) On Tue, Apr 26, 2016 at 6:02 PM, Timur Fayruzov wrote: > Thank you Till. > > I will try to run with new binaries today. As I have mentioned, the error > is reproducible only on a full dataset, so coming up with sample input data > m

Re: "No more bytes left" at deserialization

2016-04-26 Thread Timur Fayruzov
Thank you Till. I will try to run with new binaries today. As I have mentioned, the error is reproducible only on a full dataset, so coming up with sample input data may be problematic (not to mention that the real data can't be shared). I'll see if I can replicate it, but could take a bit longer.

Re: "No more bytes left" at deserialization

2016-04-26 Thread Till Rohrmann
Hi Timur, I’ve got good and not so good news. Let’s start with the not so good news. I couldn’t reproduce your problem but the good news is that I found a bug in the duplication logic of the OptionSerializer. I’ve already committed a patch to the master to fix it. Thus, I wanted to ask you, wheth

Re: "No more bytes left" at deserialization

2016-04-26 Thread Aljoscha Krettek
Could this be caused by the disabled reference tracking in our Kryo serializer? From the stack trace it looks like its failing when trying to deserialize the traits that are wrapped in Options. On Tue, 26 Apr 2016 at 10:09 Ufuk Celebi wrote: > Hey Timur, > > I'm sorry about this bad experience.

Re: "No more bytes left" at deserialization

2016-04-26 Thread Ufuk Celebi
Hey Timur, I'm sorry about this bad experience. >From what I can tell, there is nothing unusual with your code. It's probably an issue with Flink. I think we have to wait a little longer to hear what others in the community say about this. @Aljoscha, Till, Robert: any ideas what might cause thi

Re: "No more bytes left" at deserialization

2016-04-25 Thread Timur Fayruzov
Still trying to resolve this serialization issue. I was able to hack it by 'serializing' `Record` to String and then 'deserializing' it in coGroup, but boy its so ugly. So the bug is that it can't deserialize the case class that has the structure (slightly different and more detailed than I stated

Re: "No more bytes left" at deserialization

2016-04-24 Thread Timur Fayruzov
Hello Robert, I'm on 1.0.0 compiled with Scala 2.11. The second exception was an issue with a cluster (that I didn't dig into), when I restarted the cluster I was able to go past it, so now I have the following exception: java.lang.Exception: The data preparation for task 'CHAIN CoGroup (CoGroup

Re: "No more bytes left" at deserialization

2016-04-24 Thread Robert Metzger
For the second exception, can you check the logs of the failing taskmanager (10.105.200.137)? I guess these logs some details on why the TM timed out. Are you on 1.0.x or on 1.1-SNAPSHOT? We recently changed something related to the ExecutionConfig which has lead to Kryo issues in the past. On

Re: "No more bytes left" at deserialization

2016-04-24 Thread Timur Fayruzov
Trying to use ProtobufSerializer -- program consistently fails with the following exception: java.lang.IllegalStateException: Update task on instance 52b9d8ffa1c0bb7251a9731c565460eb @ ip-10-105-200-137 - 1 slots - URL: akka.tcp://flink@10.105.200.137:48990/user/taskmanager failed due to: at org.a

"No more bytes left" at deserialization

2016-04-24 Thread Timur Fayruzov
Hello, I'm running a Flink program that is failing with the following exception: 2016-04-23 02:00:38,947 ERROR org.apache.flink.client.CliFrontend - Error while running the command. org.apache.flink.client.program.ProgramInvocationException: The program execution failed: Job execu