Hey Rob, On 13 May 2016 at 15:45, Arkay <robkee...@gmail.com> wrote:
> 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? > Great to hear that you solved your problem! I'm not sure whether it's a windows peculiarity, maybe someone else could clear this up. > > 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? > You could try setting the execution mode to BATCH/BATCH_FORCED with "env.getConfig.setExecutionMode()". It is typically more expensive than the default pipelined mode, but it guarantees that no successive operations are run concurrently. > 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 :) > > :)) Let us know if you run into any more problems or have questions. Cheers, -V. Rob > > > > -- > 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. >
