Try to see of in the output of dmesg command there are some log about an OOM. The OS logs there such info. I had a similar experience recently... see [1]
Best, Flavio [1] http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-and-swapping-question-td13284.html On 12 Jun 2017 21:51, "Sebastian Neef" <gehax...@mailbox.tu-berlin.de> wrote: > Hi Stefan, > > thanks for the answer and the advise, which I've already seen in another > email. > > Anyway, I played around with the taskmanager.numberOfTaskSlots and > taskmanager.memory.fraction options. I noticed that decreasing the > former and increasing the latter lead to longer execution and more > processed data before the failure. > > The error messages and exceptions from an affected TaskManager are here > [1]. Unfortunately, I cannot find a java.lang.OutOfMemoryError in here. > > Do you have another idea or something to try? > > Thanks in advance, > Sebastian > > > [1] > http://paste.gehaxelt.in/?e669fabc1d4c15be#G1Ioq/ > ASwGUdCaK2rQ1AY3ZmCkA7LN4xVOHvM9NeI2g= >
