[
https://issues.apache.org/jira/browse/HDFS-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036977#comment-14036977
]
Hadoop QA commented on HDFS-6549:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12651329/HDFS-6549.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs hadoop-hdfs-project/hadoop-hdfs-nfs:
org.apache.hadoop.hdfs.server.datanode.TestBPOfferService
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/7173//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7173//console
This message is automatically generated.
> 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, 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)
