hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8408) MR doesn't work with a non-default ViewFS mount table and security enabled
Date Mon, 21 May 2012 19:27:41 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280401#comment-13280401

Aaron T. Myers commented on HADOOP-8408:

Thanks for the input, Daryn. I'll try changing it as you describe, and we can amend this JIRA
if it works. Do you think the fix for HDFS-3062 should also be corrected?

It's not super clear to me what the flow of control is expected to be for file systems which
don't have their own support for tokens, but rather delegate to underlying FS implementations.
Would you mind explaining it? I see this comment in FileSystem, but it doesn't make it clear
how tokens will end up getting cached for a file system which delegates token fetching:

Get a canonical service name for this file system.  The token cache is
the only user of this value, and uses it to lookup this filesystem's
service tokens.  The token cache will not attempt to acquire tokens if the
service is null.
> MR doesn't work with a non-default ViewFS mount table and security enabled
> --------------------------------------------------------------------------
>                 Key: HADOOP-8408
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8408
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 2.0.0
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>             Fix For: 2.0.1
>         Attachments: HDFS-8408.patch
> With security enabled, if one sets up a ViewFS mount table using the default mount table
name, everything works as expected. However, if you try to create a ViewFS mount table with
a non-default name, you'll end up getting an error like the following (in this case "vfs-cluster"
was the name of the mount table) when running an MR job:
> {noformat}
> java.lang.IllegalArgumentException: java.net.UnknownHostException: vfs-cluster
> {noformat}

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


View raw message