You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2014/07/01 19:40:25 UTC

[jira] [Commented] (YARN-2240) yarn logs can get corrupted if the aggregator does not have permissions to the log file it tries to read

    [ https://issues.apache.org/jira/browse/YARN-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049104#comment-14049104 ] 

Vinod Kumar Vavilapalli commented on YARN-2240:
-----------------------------------------------

[~mitdesai], this is interesting. We had seen a bunch of errors that we couldn't find the root cause for. Mind pasting the exception messages that you see on the client or the error message in the logs?

> yarn logs can get corrupted if the aggregator does not have permissions to the log file it tries to read
> --------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-2240
>                 URL: https://issues.apache.org/jira/browse/YARN-2240
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Mit Desai
>
> When the log aggregator is aggregating the logs, it writes the file length first. Then tries to open the log file and if it does not have permission to do that, it ends up just writing an error message to the aggregated logs.
> The mismatch between the file length and the actual length here makes the aggregated logs corrupted.



--
This message was sent by Atlassian JIRA
(v6.2#6252)