hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5268) NFS write commit verifier is not set in a few places
Date Sat, 28 Sep 2013 13:31:13 GMT

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

Hudson commented on HDFS-5268:
------------------------------

SUCCESS: Integrated in Hadoop-Hdfs-trunk #1536 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1536/])
HDFS-5268. NFS write commit verifier is not set in a few places. Contributed by Brandon Li
(brandonli: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1527087)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs-nfs/src/main/java/org/apache/hadoop/hdfs/nfs/nfs3/OpenFileCtx.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt

                
> NFS write commit verifier is not set in a few places
> ----------------------------------------------------
>
>                 Key: HDFS-5268
>                 URL: https://issues.apache.org/jira/browse/HDFS-5268
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: nfs
>            Reporter: Brandon Li
>            Assignee: Brandon Li
>             Fix For: 2.1.2-beta
>
>         Attachments: HDFS-5268.patch
>
>
> Each time, after server reboot a WRITE_COMMIT_VERF is created and passed to NFS client
with write or commit response. If this verifier is not correctly set in the response, some
NFS client(especially Linux client) could keep resending the same request, since it thinks
the write/commit didn't succeed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message