Registry return out of memory to download modules

[klinux]

Hello guys,

After upgrade terrakube we start to receive this error to download modules from registry.

terrakube-registry java.lang.OutOfMemoryError: Cannot reserve 6226740 bytes of direct buffer memory (allocated: 6291120, limit: 10485760)
terrakube-registry-555496bc9c-7vzmk terrakube-registry  at java.base/java.nio.Bits.reserveMemory(Unknown Source) ~[na:na]
terrakube-registry-555496bc9c-7vzmk terrakube-registry  at java.base/java.nio.DirectByteBuffer.<init>(Unknown Source) ~[na:na]
terrakube-registry-555496bc9c-7vzmk terrakube-registry  at java.base/java.nio.ByteBuffer.allocateDirect(Unknown Source) ~[na:na]
terrakube-registry-555496bc9c-7vzmk terrakube-registry  at java.base/sun.nio.ch.Util.getTemporaryDirectBuffer(Unknown Source) ~[na:na]
...

Latest stable version

[alfespa17]

Hello @klinux

Maybe you can try giving the registry pod more memory.

You can also tweak the JVM parameter related to memory using the following:

#1499 (comment)

I hope that can helps

[klinux]

I think that registry has a memory leak or other problems, I put a lot of memory and error still persists.

[klinux]

Sure,

Version: 2.23.3
Storage: GCS

I restarted the registry, I can download the module, but after 5, 6 times of the download, I started to receive this error:

terrakube-registry java.lang.OutOfMemoryError: Cannot reserve 6226740 bytes of direct buffer memory (allocated: 6291120, limit: 10485760)
terrakube-registry-555496bc9c-7vzmk terrakube-registry  at java.base/java.nio.Bits.reserveMemory(Unknown Source) ~[na:na]
terrakube-registry-555496bc9c-7vzmk terrakube-registry  at java.base/java.nio.DirectByteBuffer.<init>(Unknown Source) ~[na:na]
terrakube-registry-555496bc9c-7vzmk terrakube-registry  at java.base/java.nio.ByteBuffer.allocateDirect(Unknown Source) ~[na:na]
terrakube-registry-555496bc9c-7vzmk terrakube-registry  at java.base/sun.nio.ch.Util.getTemporaryDirectBuffer(Unknown Source) ~[na:na]
...

The module has a lot update, is a new module that we created, looks like after update the module this error happens, it's make sense?

I raise the pod RAM, to 6GB, change de parameter MaxDirectMemorySize to 32M now I'm testing with 512M, with 32M the error still happens.

Thank you

[alfespa17]

I will try to deploy the registry using a GCS tomorrow maybe I can reproduce your error, we update some of the libraries related to Google Cloud according to the release notes not sure if that could be related.

https://github.com/AzBuilder/terrakube/releases/tag/2.23.0

Can you connect to the GCS and check the size of the module? (maybe the module is to big)

[alfespa17]

When you create a new module tag terrakube clone the repository using the tag and creates a new zip file that is downloaded later from the terraform cli, maybe the zip file is too big.

[klinux]

At bucket, the module has 19MB, hummmm I think there some problems here.

[klinux]

The problem is the size of the module, someone committed the node_modules folder :(

Thank you