[
https://issues.apache.org/jira/browse/YARN-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229410#comment-15229410
]
Vinod Kumar Vavilapalli commented on YARN-4552:
-----------------------------------------------
[~djp], let me know if you can update this soon enough for 2.7.3 in a couple of
days. Otherwise, we can simply move this to 2.7.4 or 2.8 in few weeks.
> NM ResourceLocalizationService should check and initialize local filecache
> dir (and log dir) even if NM recover is enabled.
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-4552
> URL: https://issues.apache.org/jira/browse/YARN-4552
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Reporter: Junping Du
> Assignee: Junping Du
> Priority: Critical
> Attachments: YARN-4552-v2.patch, YARN-4552.patch
>
>
> In some cases, user are cleanup localized file cache for debugging/trouble
> shooting purpose during NM down time. However, after bring back NM (with
> recovery enabled), the job submission could be failed for exception like
> below:
> {noformat}
> Diagnostics: java.io.FileNotFoundException: File
> /disk/12/yarn/local/filecache does not exist.
> {noformat}
> This is due to we only create filecache dir when recover is not enabled
> during ResourceLocalizationService get initialized/started.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
