Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 08B61102A7 for ; Mon, 22 Dec 2014 16:13:14 +0000 (UTC) Received: (qmail 75304 invoked by uid 500); 22 Dec 2014 16:13:13 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 75243 invoked by uid 500); 22 Dec 2014 16:13:13 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 75230 invoked by uid 99); 22 Dec 2014 16:13:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Dec 2014 16:13:13 +0000 Date: Mon, 22 Dec 2014 16:13:13 +0000 (UTC) From: "Hari Sekhon (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-7563) NFS gateway parseStaticMap NumberFormatException MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated HDFS-7563: ------------------------------ Attachment: (was: UID_GID_Long_HashMaps.patch) > 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: Aaron T. Myers > > 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.(ShellBasedIdMapping.java:91) > at org.apache.hadoop.hdfs.nfs.nfs3.RpcProgramNfs3.(RpcProgramNfs3.java:176) > at org.apache.hadoop.hdfs.nfs.nfs3.Nfs3.(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)