You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Marco Nicosia (JIRA)" <ji...@apache.org> on 2009/01/13 21:19:02 UTC

[jira] Updated: (HADOOP-5022) [HOD] logcondense should delete all hod logs for a user, including jobtracker logs

     [ https://issues.apache.org/jira/browse/HADOOP-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marco Nicosia updated HADOOP-5022:
----------------------------------

    Priority: Blocker  (was: Major)

Thanks Hemanth. This is having a big impact on our running Hadoop clusters, so marking as blocker for 0.18.3.


> [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 Core
>          Issue Type: Bug
>          Components: contrib/hod
>            Reporter: Hemanth Yamijala
>            Assignee: Peeyush Bishnoi
>            Priority: Blocker
>             Fix For: 0.18.3
>
>
> 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.