flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arkay <robkee...@gmail.com>
Subject Re: "Memory ran out" error when running connected components
Date Fri, 13 May 2016 13:45:37 GMT
Thanks for the link, I had experimented with those options, apart from
taskmanager.memory.off-heap: true.  Turns out that allows it to run through
happily!  I don't know if that is a peculiarity of a windows JVM, as I
understand that setting is purely an efficiency improvement?

For your first question, yes I have a number of steps that get scheduled
around the same time in the job, its not really avoidable unless there are
optimizer hints to tell the system to only run certain steps on their own? 
I will try cutting the rest of the program out as a test however.

Thanks very much for your help with this, and all your excellent work on
Flink and Gelly :)


View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Memory-ran-out-error-when-running-connected-components-tp6888p6904.html
Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.

View raw message