[
https://issues.apache.org/jira/browse/HADOOP-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Chansler updated HADOOP-5022:
------------------------------------
Release Note: New logcondense option retain-master-logs indicates whether
the script should delete master logs as part of its cleanup process. By default
this option is false; master logs are deleted. Earlier versions of logcondense
did not delete master logs. (was: Implemented an option, retain-master-logs,
in logcondense support script that would indicate whether the script should
delete hadoop master logs as part of its cleanup process. By default this
option is false, that makes the change incompatible with earlier versions of
logcondense.)
Editorial pass over all release notes prior to publication of 0.21.
> [HOD] logcondense should delete all hod logs for a user, including jobtracker
> logs
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-5022
> URL: https://issues.apache.org/jira/browse/HADOOP-5022
> Project: Hadoop Common
> Issue Type: Bug
> Components: contrib/hod
> Reporter: Hemanth Yamijala
> Assignee: Peeyush Bishnoi
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: hadoop-5022-1.txt, hadoop-5022-2.txt, hadoop-5022-3.txt,
> hadoop-5022.txt
>
>
> Currently, logcondense.py does not delete jobtracker logs that it uploads to
> the DFS when the HOD cluster is deallocated. This will result in the hod-logs
> directory to slowly accumulate a whole bunch of jobtracker logs. Particularly
> for users who run a lot of user jobs, this could fill up the namespace.
> Further these directories will cause the logcondense program to keep
> repeatedly looking at these directories stressing out the namenode. So,
> logcondense.py should optionally also delete the jobtracker logs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
