Thanks for your answer Nick! I am running apache/tika:latest-full which is using 1.25. Looks like I need at least version 1.26 for https://issues.apache.org/jira/browse/TIKA-3353, but I am not sure if this is not overkill for implementing basic liveness health checks.
It's clear that –spawnChild and ForkParser are two must-haves that AFAIU are not default in apache/tika:latest-full My guess is that I also need to set the jvm heap size close to the memory resource limit for the container, but that's not ideal because the heap size would be statically configured while the memory resource limits are dynamic. Or maybe this is not necessary if I use -spawnChild? I am looking forward to your answers, thanks a lot! Cristi On Fri, May 28, 2021 at 2:55 PM Nick Burch <[email protected]> wrote: > On Thu, 27 May 2021, Cristian Zamfir wrote: > > I am running some stress tests of the latest tika server docker (not > > modified in any way, just pulled from the registry) and seeing that > after a > > few hours I see OOM in the logs. The container has a limit of 4GB set in > > K8S. I am wondering if you have any best practices on how to avoid this. > > Hopefully one of our Tika+Docker experts will be along in a minute to help > advise! > > For now, the general advice is documented at: > > https://cwiki.apache.org/confluence/display/TIKA/The+Robustness+of+Apache+Tika > > Also, which version of Tika are you on? There have been some contributions > recently around monitoring the server, which you might want to upgrade > for, eg TIKA-3353 > > Nick >
