Created on 11-02-2015 01:50 PM - edited 09-16-2022 02:47 AM
Created 11-02-2015 02:27 PM
It's not different than any typical RDBMS or Application log rotation policies. Based on the organization policies, logs can be rotated every 30 days or so to keep enough space on /var/log (Best practice is to have dedicated disk or partition of size ~ 200 GB)
Simple cron job can call a script to move logs to different location from /var/log to NFS or tape or external media.
This is helpful.
Created 11-02-2015 02:27 PM
It's not different than any typical RDBMS or Application log rotation policies. Based on the organization policies, logs can be rotated every 30 days or so to keep enough space on /var/log (Best practice is to have dedicated disk or partition of size ~ 200 GB)
Simple cron job can call a script to move logs to different location from /var/log to NFS or tape or external media.
This is helpful.
Created 11-03-2015 11:12 PM
Thanks @Neeraj - The 200GB guide line is something I can share with customers.
Created 11-03-2015 11:14 PM
Yes. I am sure they will appreciate it
Created 11-04-2015 07:22 PM
I second Ryan's comment on dedicated disk or partition for logs. that the biggest mistake made in the field is to not dedicate disk or partition to /var/log. it is not trivial to migrate logs if managed by Ambari after initial installation, although it is doable. If you fail into this situation, ask for instruction set from Hortonworks support. I had to do so and wished I had set this up initially on seperate disk