This error actually notifies us that the Tidal Master process is exhausting its Java heap memory. Even though the server has sufficient physical RAM, and the application has been running without issues for months, it has still ended up with a Java heap memory error. If you try to recycle the Master agent, this should be a temporary fix, as it will clear the heap. However, after clearing the heap memory usage will continue to build up until it reaches the configured limit. When it reaches the limit, of course, this will cause the Java clients to become unresponsive or inaccessible. This type of problem typically arises when the workload is heavy or if there is a memory leak. This usually causes objects to hold onto other objects in the heap than the expected time frame.
The issue is not related to the operating system or the JVM itself. It's mainly because of how much heap the Master JVM is configured to use and how memory is being consumed over time. It’s better to increase the JVM heap size, enable GC logging to observe memory behavior, and capture thread or heap dumps before restarting the service. Doing this will help you identify and permanently resolve the root cause, instead of relying on daily restarts. To learn more interesting details about the OutOfMemoryError: Java heap space error, you can check out this blog, How to Solve OutOfMemoryError: Java heap space. This will give you more insights about this Java heap space error.
