[
https://issues.apache.org/jira/browse/MAPREDUCE-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435262#comment-13435262
]
Jason Lowe commented on MAPREDUCE-4296:
---------------------------------------
Getting close, a few more points:
* We're checking the permission of each app log directory, but the permission
of the user log directory above them could prevent us from deleting the app
directory.
* Checking for group write doesn't imply we'd still be able to delete. I'm
thinking in particular of the setup issues discussed in MAPREDUCE-4557.
Rather than trying to avoid the errant deletes and potentially screwing up
those checks, we could just proceed with the delete attempt and not log a giant
exception if the error is a permission problem. We could still end up logging
a line per application in a misconfigured user log directory, but that's better
than logging dozens of lines for a full exception trace that isn't helpful for
permission issues anyway.
> remove old aggregated logs
> --------------------------
>
> Key: MAPREDUCE-4296
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4296
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.3
> Reporter: Thomas Graves
> Assignee: Robert Joseph Evans
> Attachments: 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
