hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ming Ma (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-2050) Fix LogCLIHelpers to create the correct FileContext
Date Mon, 12 May 2014 21:56:15 GMT

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

Ming Ma updated YARN-2050:

    Attachment: YARN-2050.patch

Papreduce CLI and yarn CLI pass the configuration to LogCLIHelpers. LogCLIHelpers use the
same configuration to create remoteRootLogDir and remoteAppLogDir, etc. in dumpAllContainersLogs.
The fix is to use the same configuration to create FileContext.

To follow up on [~jlowe]'s comments,

1. remoteAppLogDir.toUri().getScheme() returns null and AbstractFileSystem.createFileSystem
doesn't like it if dumpAllContainersLogs calls FileContext.getFileContext(remoteAppLogDir.toUri()).

2. If caller of LogCLIHelpers doesn't setConf ahead of time, dumpAllContainersLogs will get
null pointer exception when it tries to get remoteRootLogDir.

> Fix LogCLIHelpers to create the correct FileContext
> ---------------------------------------------------
>                 Key: YARN-2050
>                 URL: https://issues.apache.org/jira/browse/YARN-2050
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>         Attachments: YARN-2050.patch
> LogCLIHelpers calls FileContext.getFileContext() without any parameters. Thus the FileContext
created isn't necessarily the FileContext for remote log.

This message was sent by Atlassian JIRA

View raw message