System Scheduled Event ClusterManagement-CleanupOrphanedFiles

0
Hello Mendix Community,   the Mendix System Scheduled Event "ClusterManagement-CleanupOrphanedFiles" deletes the files from the file system that are already deleted from system.FileDocument.   This Mendix Scheduled Event runs every 30 minutes and the max. amount of files to be deleted in a run is 1000 files.   Is it possible to configure this system scheduled event?   We are using a Mendix Server on Premise with Mendix Version 10.24.4 Thanks in advance. Best regrards   Uwe
asked
3 answers
0

I would suggest reaching out to Mendix Support directly to see if they have an undocumented way to do this. It feels like there should be a way to do this for On Premise users if you have direct access to the hardware.

 

Good luck

answered
1

As proposed by Ahmet and Robert I raised a Mendix Support Ticket and I got the following answer:

>>

You can configure this using com.mendix.storage.PerformDeleteFromStorage . You can find more information on this here.

It runs every ClusterManagerActionInterval.

<<

For our use case we set the parameter ClusterManagerActionInterval to 300000 ms (5 mins) by adding it to the Custom Settings in the Mendix Console.

After restarting the System Scheduled Event "ClusterManagement-CleanupOrphanedFiles" runs every 5 mins.

 

Hint:

by changing the ClusterManagerActionInterval also the other System Scheduled Events from the Cluster management are affected:

  • ClusterManagement-CleanupProcessedTasks
  • ClusterManagement-CleanupBackgroundJobs
  • ClusterManagement-CleanupTmpDocuments
  • ClusterManagement-CleanupScheduledEvents
  • ClusterManagement-CleanupSessions
  • ClusterManagement-CleanupOfflineSyncHistory
  • ClusterManagement-CleanupOfflineGUIDs
  • ClusterManagement-UnblockUsers
  • ClusterManagement-MigrateOldFiles
answered
0

You cannot configure this system scheduled event (ClusterManagement-CleanupOrphanedFiles) in a supported way from Studio Pro or standard settings, such as changing the interval or the max number of files per run. This behavior is part of Mendix Runtime’s internal cluster management mechanism.

What other values were you trying to change, and why do you need to change it? Maybe we can think about an alternative approach based on that.

answered