On DTR 2.2.1, the
dtr-api container has been known to steadily use memory until DTR is unavailable, even if the cluster is not busy.
This has been resolved in DTR 2.2.3. Upgrading to DTR 2.2.3 will fix this issue. For details on upgrading DTR, refer to the following: