hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo Nicholas Sze (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7926) NameNode implementation of ClientProtocol.truncate(..) is not idempotent
Date Fri, 13 Mar 2015 06:45:38 GMT

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

Tsz Wo Nicholas Sze commented on HDFS-7926:

> ... for a file being written or appended, truncate will still return false if the oldlength
happens to be same as newlength. It should throw an exception in this scenario. ...

That's true.  Will update the patch.

> 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
>         Attachments: h7926_20150313.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

View raw message