TjahziInitializer causing Out of Memory Error, when running in Docker Container about tjahzi HOT 3 CLOSED

@tkowalcz Thanks a lot for the explanation. Sorry for the late reply, took a while to test. It's working as expected now. Closing the ticket. Thanks again :)

from tjahzi.

Hi,

TL;DR: set useOffHeapBuffer=false config option so that data structures used by Tjahzi will be allocated on regular Java heap instead of off-heap.

I am not very versed in Docker usage, but according to your output I think this is what happens:

• You have 18761956K (~18GB) of available memory.
• JVM old gen will take 18103971K (17,2GB) out of it.
• Metaspace and code cache will take ~382MB
• Thread stacks (-Xss1M) will take 250MB (Thread Count: 250 * 1M)

If I am correct this totals to 18751715K so the container has about 10MB of free memory.
This lines up nicely with -XX:MaxDirectMemorySize=10M setting that allows the java app to allocate at most 10M of
off-heap data.

To fix this you need to increase MaxDirectMemorySize while decreasing other settings OR set Tjahzi to allocate less than 10M of off-heap data.

Let me elaborate on that last option. While configuring Tjahzi you can set useOffHeapBuffer=false so that data structures used by Tjahzi will be part of a regular Java heap. I do not expect that this would have significant performance impact on the application.

You can also set bufferSizeMegabytes to value lower than 10M from its default value of 32M. This can impact log delivery if Tjahzi cannot keep up sending data to Loki while application produices the logs into the buffer.

from tjahzi.

@akhilvpsharma doe this explanation help and fixes the issue or do you need any more assistance?

from tjahzi.