Hello,
I have reviewed your hs_err_pid report but couldn't find any issues.
To comprehensively diagnose potential problems, consider utilizing the open source yCrash script which will capture 360-degree application level artifacts (like GC logs, 3 snapshots of thread dumps, heap dumps) and system level artifacts (like top, top -H, netstat, vmstat, iostat, dmesg, diskusage, kernel parameters...). Once you have these data, either you can manually analyze them or upload it to yCrash tool. Tool analyzes all these dataset and generates an instant root cause analysis report.
Would you be willing to execute the yCrash script before the pod crashes? Kubernetes offers lifecycle hooks that allow for operations before the pod crashes. You can leverage the preStop hook to perform actions just before the pod crashes. An example of using the preStop hook to capture artifacts before a pod restart can be found here:
To find all the configuration parameters that are available, please consult the documentation link provided below:
https://docs.ycrash.io/ycrash-agent/all-agent-arguments.html#all-arguments
Edit your Comment