Hi, I'm currently running an app on-premise in production which is encountering a rapid growth in terms of disk usage. After investigating this thoroughly, this seems to be caused by Mendix deleting records in the System.FileDocument table, but not deleting the corresponding files on the disk. Because of this, the files on our production environment are never deleted adequately which has led to the files becoming orphans as they do not have a matching record in the database anymore. The issue doesn't present itself locally, nor on the acceptance environment. Some more context to the case: The app runs on Mendix version 8.4.2 We recently migrated the Mendix app to a new runtime and database server. On the old server, the situation described above didn't seem to cause an issue. As this didn't seem to pose an issue on the old server, I suspected that the issue might be caused by insufficient permissions being granted to the Mendix Service User. However, our architecture consists of only a single runtime server which runs both our acceptance and production environment, while both environments utilize the same Mendix Service User (hence having the same permissions). I did not change the default value of the com.mendix.storage.PerformDeleteFromStorage runtime setting. What could be causing the fact that Mendix isn't deleting the corresponding files on solely our production environment and how do I fix this? Thank you for your reply in advance!
↧