Yes, this is normal. These logs are created by /opt/kaltura/dwh/etlsource/execute/etl_hourly.sh which, as its name may imply, runs every hour:)
This is triggered from here:
/etc/cron.d/kaltura-dwh
Once the hourly run concludes, you can remove the logs but I recommend that, if you choose to do so, first grep -q ERROR on the log file and check the RC to ensure it includes no erroneous patterns before removal. These logs are not needed for runtime but can help in the event issues occur.
This script wastefully creates many rotated files.
For example, etl_hourly-20170810-00.log-20170811.gz, etl_hourly-20170810-00.log-20170812.gz,
etl_hourly-20170810-00.log-20170813.gz, …
So that, I am using following script as /opt/kaltura/app/configurations/logrotate/kaltura_dwh.
This script rotates non etl logs , for example log_aggregation_perform_aggregations.log.
Unfortunately, updating of Kaltura CE will return kaltura_dwh back to the original script.
So that, I hope the Kaltura CE will adopt such a function or script.
This sounds very interessting, because I took also notice that kaltura is generating a lot of log files…
I’m not so familar with cron jobs. Does the posted cron job work just by editing the kaltura_dw file first and then creating a file called “etl-cleanup” under /etc/cron.d/ with the following content:
Or do I have to configure something additionaly?
What’s about the /opt/kaltura/log directory? Is it also useful to delete some log files there from time to time?
If you use my script and cron file, you do not need to modify other files.
My log-rotation script makes 30 rotation files about non-etl log files.
And, my cron file deletes etl log files generated more than 30 days ago.
You probably should modify “30” in the “kaltura_dwh” and “etl-cleanup”.
If you do not use kaltura_dwh and any cron, the elt log files continues to be created permanently, and, non-etl log files keeps increasing file size permanently.
But, originally kaltura_dwh creates a lot of unnecessary etl log files.
If you want to avoid this trend, you should use the log-rotation and the cron.