[
https://issues.apache.org/jira/browse/HDFS-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated HDFS-7926:
------------------------------------------
Labels: 2.6.1-candidate (was: )
Adding back 2.6.1-candidate label for tracking purposes. Will remove it once
2.6.1 is done.
> 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
> Labels: 2.6.1-candidate
> 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)
