I use Kaltura configured with external storage and I configured it to remove from local all exported files to remote storage.
I see that when I delete a media entry from Kaltura (via KMC or via API), Kaltura’s batch process don’t deletes the source and flavors from remote storage.
anyone can help me to understand if exists a workaround to do it?
we had investigated this about a year ago and at the time this functionality was not working. To my Knowledge it is STILL not working, at least for S3 remote storage.
As it stands now, when deleting an entry from the API, it should also delete it from the remote storage, assuming the remote storage is set to “automatic” state.
An entry deletion via the API [which happens when using KMC or any other Kaltura management I/F as well], is suppose to trigger a deletion job from the remote storage.
These jobs are kept in the scheduler_worker table which you can look at with say:
mysql> select * from scheduler_worker where name like ‘%KAsyncStorageDelete%’\G
you can also check this specific job log under /opt/kaltura/log/batch/storagedelete*log
This is provided you have enabledWorkers.KAsyncStorageDelete set to 1 in /opt/kaltura/app/configurations/batch/batch.ini