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 "Junping Du (JIRA)" <ji...@apache.org> on 2016/04/05 20:27:25 UTC
[jira] [Commented] (YARN-4552) NM ResourceLocalizationService
should check and initialize local filecache dir (and log dir) even if NM
recover is enabled.
[ https://issues.apache.org/jira/browse/YARN-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226850#comment-15226850 ]
Junping Du commented on YARN-4552:
----------------------------------
Hi [~vinodkv], I will rebase the patch soon. I think we are getting close on this.
> 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)