It just happened again and i solved with the -X parameter to the JVM
Thank you!
Il giorno 11/mag/2015, alle ore 21:50, Stephan Ewen
mailto:se...@apache.org>> ha scritto:
What you see is that the effect of extremely little memory arriving at the
memory manager.
Given that you are saying that
What you see is that the effect of extremely little memory arriving at the
memory manager.
Given that you are saying that restarting the machine helps (or using a
downloaded version of Flink), the reason is probably that you do not
configure the JVM memory (in which case Java grabs a bit of the sy
Hi,
thank you for your fast answer
next time it happens i will try
Michele
Il giorno 10/mag/2015, alle ore 19:45, Fabian Hueske
mailto:fhue...@gmail.com>> ha scritto:
Hi Michele,
Flink manages its own memory using the MemoryManager. When a Flink worker
(TaskManager) starts, the MemoryManage
Hi Michele,
Flink manages its own memory using the MemoryManager. When a Flink worker
(TaskManager) starts, the MemoryManager allocates a certain share of the
JVM's free memory as MemorySegments: Default size of a MemorySegment is
32KB. When a Flink program is executed, the MemoryManager hands a c
