per https://github.com/IQSS/dataverse/issues/10667 JSF seems to leave behind artifacts of upload activity, even on S3 datastores with direct-upload defined and in use. one easy workaround suggested by @landreev is to set <jvm-options>-Ddataverse.files.uploads=/tmp</jvm-options> which should subject these uploads to tmpdir cleaner (files not accessed in 10 calendar days are removed). let's add this as a jvm-option until this bug gets fixed either in the existing code or Dataverse moves to the SPA.
per https://github.com/IQSS/dataverse/issues/10667 JSF seems to leave behind artifacts of upload activity, even on S3 datastores with direct-upload defined and in use. one easy workaround suggested by @landreev is to set
<jvm-options>-Ddataverse.files.uploads=/tmp</jvm-options>which should subject these uploads to tmpdir cleaner (files not accessed in 10 calendar days are removed). let's add this as a jvm-option until this bug gets fixed either in the existing code or Dataverse moves to the SPA.