On Thu, May 27, 2021 at 11:31 PM Cristian Zamfir <[email protected]> wrote:
> Hi, > > 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. > For instance: > - should I set the JVM heap size to match the memory limit on the > container? > - is there a way to restart in case of OOM? > - should I use spawnChild? > A related question is about health checks - a simple way to implement external health checks would be to call any API entrypoint such as /tika with a couple of bytes of input and check the reply, but I thought I would check for a dedicated API for this. Thanks!
