0

Cron Job Clean Up Schedule

As the Scheduler Monitor runs, it stores data in a related database. Over time, this database can grow very large and slow down functionality. To reduce the size of the database, the system cleans data out of the data base daily, removing data that is more than 7 days old by default.

The daily cleanup also removes login tokens that can no longer be used, including tokens of ended logins after 2 days and refresh tokens of connected apps once they have expired. The system removes stored tokens of external identity providers when no login uses them anymore and they were not used for the retention period (_global.cleanup.retention_period in the server settings, default 7 days). When tokens are stored in an external database (data source __tokenmgnt), the system cleans that database as well.

For large systems where many cronjobs run each day, you may want to reduce the retention period. For other systems you may want to keep the logs for longer.

To change the cleanup schedule add the following text to the system settings.cfg file located at <installation-path>\dat\settings.cfg. Note that a standard installation will not have this configuration setting already in place and  you will need to add it.

The example shows the setting when cronjob files need to be kept for 1 day).

_session = {
    SCHEDULER = {
         retention_period = 1
                 }
         }

Reply

null

Content aside

  • 3 yrs agoLast active
  • 23Views
  • 3 Following