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-7926) NameNode implementation of ClientProtocol.truncate(..) is not idempotent
Date Sat, 14 Mar 2015 11:36:42 GMT

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

Hudson commented on HDFS-7926:
------------------------------

FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #132 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/132/])
HDFS-7926. NameNode implementation of ClientProtocol.truncate(..) is not idempotent. Contributed
by Tsz Wo Nicholas Sze (brandonli: rev f446669afb5c3d31a00c65449f27088b39e11ae3)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockInfoContiguousUnderConstruction.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFileTruncate.java


> NameNode implementation of ClientProtocol.truncate(..) is not idempotent
> ------------------------------------------------------------------------
>
>                 Key: HDFS-7926
>                 URL: https://issues.apache.org/jira/browse/HDFS-7926
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>             Fix For: 2.7.0
>
>         Attachments: h7926_20150313.patch, h7926_20150313b.patch
>
>
> If dfsclient drops the first response of a truncate RPC call, the retry by retry cache
will fail with "DFSClient ... is already the current lease holder".  The truncate RPC is annotated
as @Idempotent in ClientProtocol but the NameNode implementation is not.



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

Mime
View raw message