Re: JVM crash - SIGSEGV in ZIP_GetEntry

2017-12-19 Thread Dawid Wysakowicz
Thanks Gyula, It kind of helped. I did remove some KryoSerializers here and there and it started working, but don’t understand it fully. Will try to understand and reproduce it, as soon as I have some spare time. > On 17 Dec 2017, at 17:52, Gyula Fóra wrote: > > Hi, > I have seen similar erro

Re: JVM crash - SIGSEGV in ZIP_GetEntry

2017-12-17 Thread Gyula Fóra
Hi, I have seen similar errors when trying to serialize Kryo-typeserializers with Flink type infos accidentally. Maybe that helps :) Gyula On Sun, Dec 17, 2017, 15:52 Dawid Wysakowicz wrote: > Just as a follow-up I tried disabling mmap with > sun.zip.disableMemoryMapping, but it did not help.

Re: JVM crash - SIGSEGV in ZIP_GetEntry

2017-12-17 Thread Dawid Wysakowicz
Just as a follow-up I tried disabling mmap with sun.zip.disableMemoryMapping, but it did not help. This time I got only Java stack: Stack: [0x7f9060757000,0x7f9060858000], sp=0x7f9060856350, free space=1020k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native

JVM crash - SIGSEGV in ZIP_GetEntry

2017-12-17 Thread Dawid Wysakowicz
Hi, Recently we observe regular taskmanager's JVM crashes just about a minute from the start of our Flink job. We run flink 1.3.2 on YARN (2.6.2.0-205). Java version: JRE version: Java(TM) SE Runtime Environment (8.0_112-b15) (build 1.8.0_112-b15) # Java VM: Java HotSpot(TM) 64-Bit Server VM (2