I have OpenKM installed on a virtualized server in AWS with CentOS 7 as the operating system. It is configured with Tomcat 9.0, and the database is on MariaDB. During production hours, the system experiences frequent crashes. The temporary solution to address the issue has been to stop Tomcat and restart the server. However, these incidents are occurring more frequently. When monitoring the machine with 'top,' it's evident that the MariaDB service is consuming the most resources. The server is using a substantial instance type, so the issue does not seem to be related to machine resource constraints.
We discovered that part of the problem is the mysqld service, which is exceeding resource limits because the 'trash' folder is syncing with the database. We need to find out how to make OpenKM synchronize without including the 'trash' folder.
We discovered that part of the problem is the mysqld service, which is exceeding resource limits because the 'trash' folder is syncing with the database. We need to find out how to make OpenKM synchronize without including the 'trash' folder.