Re: Different results on local and on cluster

2016-07-18 Thread Ufuk Celebi
Thanks for reporting back! On Mon, Jul 18, 2016 at 10:13 AM, Flavio Pompermaier wrote: > Hi to all, > I forgot to close this thread. In the end the error was (fortunately) in my > code, since I use the "reuse strategy" and in one case I forgot to reset the > field of a POJO I was filling in a map

Re: Different results on local and on cluster

2016-07-18 Thread Flavio Pompermaier
Hi to all, I forgot to close this thread. In the end the error was (fortunately) in my code, since I use the "reuse strategy" and in one case I forgot to reset the field of a POJO I was filling in a map function. So, every time I was running the job the error was in a different output object. Than

Re: Different results on local and on cluster

2016-07-04 Thread Flavio Pompermaier
Sorry I wanted to write Kryo but I'm on my mobile On 4 Jul 2016 12:34 p.m., "Flavio Pompermaier" wrote: > Because I don't see any good reason for that...maybe also all keyo > serialization errors that I have from time to time could be symptomatic of > some other error in how Flink manage t

Re: Different results on local and on cluster

2016-07-04 Thread Flavio Pompermaier
Because I don't see any good reason for that...maybe also all keyo serialization errors that I have from time to time could be symptomatic of some other error in how Flink manage the ibternal buffers...but also this is just another personal guess I did.. On 4 Jul 2016 12:29 p.m., "Ufuk Celebi"

Re: Different results on local and on cluster

2016-07-04 Thread Ufuk Celebi
It's not possible to tell. You would have to look into the logs of the job manager to check what happened. The not killed task manager could have re-connected to the job manager, if it was restarted quickly after the failure. Why do you think that the task manager would influence the job result tho

Re: Different results on local and on cluster

2016-07-04 Thread Flavio Pompermaier
No, I haven't. I fear that unkilled taskmanger could have been the cause of this problem. Last day I run the job and I discovered that on some node there was some zombie taskmanger yhat wasn't terminated during the stop-cluster. What do you think?What happens in this situations?old taskmanager are

Re: Different results on local and on cluster

2016-07-04 Thread Ufuk Celebi
I guess Aljoscha was referring to whether you also have broadcasted input or something like it? On Fri, Jul 1, 2016 at 7:05 PM, Flavio Pompermaier wrote: > what do you mean exactly? > > On 1 Jul 2016 18:58, "Aljoscha Krettek" wrote: >> >> Hi, >> do you have any data in the coGroup/groupBy operat

Re: Different results on local and on cluster

2016-07-01 Thread Flavio Pompermaier
what do you mean exactly? On 1 Jul 2016 18:58, "Aljoscha Krettek" wrote: > Hi, > do you have any data in the coGroup/groupBy operators that you use, > besides the input data? > > Cheers, > Aljoscha > > On Fri, 1 Jul 2016 at 14:17 Flavio Pompermaier > wrote: > >> Hi to all, >> I have a Flink job

Re: Different results on local and on cluster

2016-07-01 Thread Aljoscha Krettek
Hi, do you have any data in the coGroup/groupBy operators that you use, besides the input data? Cheers, Aljoscha On Fri, 1 Jul 2016 at 14:17 Flavio Pompermaier wrote: > Hi to all, > I have a Flink job that computes data correctly when launched locally from > my IDE while it doesn't when launche