hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yongjun Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7563) NFS gateway parseStaticMap NumberFormatException
Date Wed, 31 Dec 2014 22:12:14 GMT

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

Yongjun Zhang commented on HDFS-7563:
-------------------------------------

Thanks Hari for reporting the issue.

I uploaded a patch to reuse existing code introduced for HDFS-6361. 

Hi [~brandonli], thanks your help with HDFS-6361 earlier. The patch here is very small, wonder
if you could help doing a review? 

Wish you all a happy new year!


> NFS gateway parseStaticMap NumberFormatException
> ------------------------------------------------
>
>                 Key: HDFS-7563
>                 URL: https://issues.apache.org/jira/browse/HDFS-7563
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: nfs
>    Affects Versions: 2.6.0
>         Environment: HDP 2.2
>            Reporter: Hari Sekhon
>            Assignee: Yongjun Zhang
>         Attachments: HDFS-7563.001.patch, UID_GID_Long_HashMaps.patch
>
>
> When using the new NFS UID mapping for the HDFS NFS gateway I've discovered that my Windows
7 workstation at this bank is passing UID number 4294xxxxxx but entering this in the /etc/nfs.map
in order to remap that to a Hadoop UID prevents the NFS gateway from restarting with the error
message:
> {code}Exception in thread "main" java.lang.NumberFormatException: For input string: "4294xxxxxx"
>         at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
>         at java.lang.Integer.parseInt(Integer.java:495)
>         at java.lang.Integer.parseInt(Integer.java:527)
>         at org.apache.hadoop.security.ShellBasedIdMapping.parseStaticMap(ShellBasedIdMapping.java:318)
>         at org.apache.hadoop.security.ShellBasedIdMapping.updateMaps(ShellBasedIdMapping.java:229)
>         at org.apache.hadoop.security.ShellBasedIdMapping.<init>(ShellBasedIdMapping.java:91)
>         at org.apache.hadoop.hdfs.nfs.nfs3.RpcProgramNfs3.<init>(RpcProgramNfs3.java:176)
>         at org.apache.hadoop.hdfs.nfs.nfs3.Nfs3.<init>(Nfs3.java:45)
>         at org.apache.hadoop.hdfs.nfs.nfs3.Nfs3.startService(Nfs3.java:66)
>         at org.apache.hadoop.hdfs.nfs.nfs3.Nfs3.main(Nfs3.java:72)
> {code}
> The /etc/nfs.map file simply contains
> {code}
> uid 4294xxxxxx 1yyyy
> {code}
> It seems that the code at {code}hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/ShellBasedIdMapping.java{code}
> is expecting an integer at line 318 of the parseStaticMap method: {code}int remoteId
= Integer.parseInt(lineMatcher.group(2));
> int localId = Integer.parseInt(lineMatcher.group(3));{code}
> This UID does seem very high to me but it has worked successfully on a MapR-FS NFS share
and stores files created with that UID over NFS.
> The UID / GID mappings for the HDFS NFS gateway will need to be switched to using Long
to accomodate this, I've attached a patch for the parsing and UID/GID HashMaps.
> Regards,
> Hari Sekhon
> http://www.linkedin.com/in/harisekhon



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message