You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Alejandro Fernandez (JIRA)" <ji...@apache.org> on 2014/08/11 05:11:12 UTC
[jira] [Updated] (AMBARI-6808) Ambari Agent DataCleaner should
delete log files when a max size in MB is reached
[ https://issues.apache.org/jira/browse/AMBARI-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Fernandez updated AMBARI-6808:
----------------------------------------
Summary: Ambari Agent DataCleaner should delete log files when a max size in MB is reached (was: Ambari Agent log files should also be limited by size, since can quickly fill up a VM)
> Ambari Agent DataCleaner should delete log files when a max size in MB is reached
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-6808
> URL: https://issues.apache.org/jira/browse/AMBARI-6808
> Project: Ambari
> Issue Type: Improvement
> Components: agent
> Affects Versions: 1.6.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 1.7.0
>
>
> The log files in /var/log/ambari-agent can sometimes quickly fill up VMs. The current policy allows running the DataCleaner every x hours (typically 1), and delete files older than y days (typically 30).
> There is one bug that structured-out-####.json and command-####.json files are not currently deleted by the DataCleaner.
> The other ask is to allow deleting the oldest files first when the total space used for log files exceeds z MB (typically 100, but can be as high as 10 GB).
--
This message was sent by Atlassian JIRA
(v6.2#6252)