hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Graves (JIRA)" <j...@apache.org>
Subject [jira] [Moved] (YARN-25) remove old aggregated logs
Date Fri, 17 Aug 2012 20:29:37 GMT

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

Thomas Graves moved MAPREDUCE-4296 to YARN-25:
----------------------------------------------

          Component/s:     (was: mrv2)
     Target Version/s:   (was: 0.23.3, 2.1.0-alpha)
    Affects Version/s:     (was: 0.23.3)
                       0.23.3
         Release Note:   (was: When upgrading if log aggregation is enabled and yarn.log-aggregation.retain-seconds
is set so that logs are going to be deleted, a cluster administrator should change the permissions
on all user's logs to be 770.

hadoop fs -chmod -R 770 <log-dir>/*

Please be sure that <log-dir> itself is not modified.

Added in new config yarn.log-aggregation.retain-seconds.
How long to keep aggregation logs before deleting them.  -1 disables.  Be careful set this
too small and you will spam the name node.)
             Workflow: jira  (was: no-reopen-closed, patch-avail)
                  Key: YARN-25  (was: MAPREDUCE-4296)
              Project: Hadoop YARN  (was: Hadoop Map/Reduce)
    
> remove old aggregated logs
> --------------------------
>
>                 Key: YARN-25
>                 URL: https://issues.apache.org/jira/browse/YARN-25
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 0.23.3
>            Reporter: Thomas Graves
>            Assignee: Robert Joseph Evans
>         Attachments: MR-4296.txt, MR-4296.txt, MR-4296.txt, MR-4296.txt
>
>
> Currently the aggregated user logs under NM_REMOTE_APP_LOG_DIR are never removed.  We
should have mechanism to remove them after certain period.
> It might make sense for job history server to remove them.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message