You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enduro (0.41.7) seems to be filling up the processing directory with blobs and extract-folder.
Client is configuring [[pipeline]] → processingDir = /var/enduro/processing
The documentation does not state a default path for some reason.
On one of their submissions we preserved around 500GB worth of AIPs during 10 hours, starting with an empty processing directory. Enduro then crashed with a database error because it had filled the /var partition (934GB in /var/enduro/processing).
Temporary workaround put in place to run an hourly cron job, deleting everything older than 6 hours from /var/enduro/processing.
But wondering if enduro could clean up temporary files as part of the workflow.
The text was updated successfully, but these errors were encountered:
Enduro (0.41.7) seems to be filling up the processing directory with blobs and extract-folder.
Client is configuring [[pipeline]] → processingDir = /var/enduro/processing
The documentation does not state a default path for some reason.
On one of their submissions we preserved around 500GB worth of AIPs during 10 hours, starting with an empty processing directory. Enduro then crashed with a database error because it had filled the /var partition (934GB in /var/enduro/processing).
Temporary workaround put in place to run an hourly cron job, deleting everything older than 6 hours from /var/enduro/processing.
But wondering if enduro could clean up temporary files as part of the workflow.
The text was updated successfully, but these errors were encountered: