Enough console output from the Trino worker container can cause an OOM for vector container

Affected Stackable version

24.3

Affected Trino version

414

Current and expected behavior

I have observed that in some cases with a lot of console output from the Trino worker container can cause the Vector container to crash on an OOM and thereby restart the whole pod.

I expect the Trino worker to be able to run without restarting.

Possible solution

Change the default settings for the vector container to have a bit more memory to work with or add a possibility to more easily set it might be nice.

I have added a podOverride section for the TrinoCluster section to increase the vectors memory settings to try and resolve the issue.

Additional context

I don't know have critical this is but I thought I should report it anyway. In case you don't find it useful, feel free to close the bug.

Environment

Client Version: v1.29.10
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.10

Would you like to work on fixing this bug?

maybe

The issue names the TrinoCluster podOverride and Vector container memory settings, but no repository files or tests. Start by locating the TrinoCluster pod configuration and reproducing the worker's high-console-output case; done means the Vector container no longer OOMs and the Trino worker pod remains running.