Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 9 Dec 2014 17:28:13 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12760404.1418119887000.110849.1418146093643@Atlassian.JIRA>
In-Reply-To: <JIRA.12760404.1418119887000@Atlassian.JIRA>
References: <JIRA.12760404.1418119887000@Atlassian.JIRA>
 <JIRA.12760404.1418119887169@arcas>
Subject: [jira] [Commented] (HDFS-7499) Add NFSv4 + Kerberos / client
 authentication support
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Allen Wittenauer commented on HDFS-7499:
----------------------------------------

RFC-compliant NFSv3 can also do Kerberos, it is marked as an optional feature and many implementations do not implement it. Sun fixed this mistake; RFC-compliant NFSv4 requires Kerberos support.

That said, NFSv4 is a MUCH MUCH MUCH better fit for HDFS than NFSv3, due to the open and close semantics. 

> Add NFSv4 + Kerberos / client authentication support
> ----------------------------------------------------
>
>                 Key: HDFS-7499
>                 URL: https://issues.apache.org/jira/browse/HDFS-7499
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>    Affects Versions: 2.4.0
>         Environment: HDP2.1
>            Reporter: Hari Sekhon
>
> We have a requirement for secure file share access to HDFS on a kerberized cluster.
> This is spun off from HDFS-7488 where adding Kerberos to the front end client was considered, I believe this would require NFSv4 support?


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