Kubernetes new pod created, old deleted

Question

I have a nodejs (nestjs) application running in a pod which downloads large csv files and then uploads these to a database (mysql, typeorm)

I was tailing the logs to see the progress of the csv download and database insert Suddenly a new pod is created and the nestjs application is then started (I can see that in the logs of the new pod). I can not find any errors anywhere, the new pod does not have any and the old pod does not exist anymore.

Everything seem to work fine with smaller amount of csv files but the one I am experiencing this in has over 1000 csv files and many of those are 300-400mb

Does anyone know what can cause this kind of behavior (or how I find any errors that might have caused this) ?

Answer 1

Exit codes are used by container engines, when a container terminates, to report why it was terminated.Exit Code 139 means that the container received a SIGSEGV signal from the operating system. This indicates a segmentation error – a memory violation, caused by a container trying to access a memory location to which it does not have access. There are three common causes of SIGSEGV errors:

1. Coding error—container process did not initialize properly, or it tried to access memory through a pointer to previously freed memory
2. Incompatibility between binaries and libraries—container process runs a binary file that is not compatible with a shared library, and thus may try to access inappropriate memory addresses
3. Hardware incompatibility or misconfiguration—if you see multiple segmentation errors across multiple libraries, there may be a problem with memory subsystems on the host or a system configuration issue.

Learn more about the SIGKILL Signal here .

Also you can refer to the following doc for more information regarding exit code 139.