Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 17 Jun 2014 01:51:02 +0000 (UTC)
From: "Aaron T. Myers (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12721565.1402967256852.143027.1402969862176@arcas>
In-Reply-To: <JIRA.12721565.1402967256852@arcas>
References: <JIRA.12721565.1402967256852@arcas>
Subject: [jira] [Updated] (HDFS-6549) Add support for accessing the NFS
 gateway from the AIX NFS client
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aaron T. Myers updated HDFS-6549:
---------------------------------

    Attachment: HDFS-6549.patch

Here's a patch which addresses the issue by introducing an "AIX compatibility mode" configuration setting. When this is enabled, very slight behavior changes are introduced in the case of COMMITs and READDIR/READDIRPLUS calls as described above. No other behavior changes are introduced as part of this change.

In addition to the provided test case, I've also tested this manually from an AIX client machine. It works as expected.

Please review.

> Add support for accessing the NFS gateway from the AIX NFS client
> -----------------------------------------------------------------
>
>                 Key: HDFS-6549
>                 URL: https://issues.apache.org/jira/browse/HDFS-6549
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: nfs
>    Affects Versions: 2.4.0
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>         Attachments: HDFS-6549.patch
>
>
> We've identified two issues when trying to access the HDFS NFS Gateway from an AIX NFS client:
> # In the case of COMMITs, the AIX NFS client will always send 4096, or a multiple of the page size, for the offset to be committed, even if fewer bytes than this have ever, or will ever, be written to the file. This will cause a write to a file from the AIX NFS client to hang on close unless the size of that file is a multiple of 4096.
> # In the case of READDIR and READDIRPLUS, the AIX NFS client will send the same cookie verifier for a given directory seemingly forever after that directory is first accessed over NFS, instead of getting a new cookie verifier for every set of incremental readdir calls. This means that if a directory's mtime ever changes, the FS must be unmounted/remounted before readdir calls on that dir from AIX will ever succeed again.
> From my interpretation of RFC-1813, the NFS Gateway is in fact doing the correct thing in both cases, but we can introduce simple changes on the NFS Gateway side to be able to optionally work around these incompatibilities.


--
This message was sent by Atlassian JIRA
(v6.2#6252)