You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org> on 2015/03/13 04:05:38 UTC

[jira] [Resolved] (HDFS-7925) truncate RPC should not be considered as idempotent

     [ https://issues.apache.org/jira/browse/HDFS-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jitendra Nath Pandey resolved HDFS-7925.
----------------------------------------
    Resolution: Duplicate

Duplicate of HDFS-7926

> truncate RPC should not be considered as idempotent
> ---------------------------------------------------
>
>                 Key: HDFS-7925
>                 URL: https://issues.apache.org/jira/browse/HDFS-7925
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.7.0
>            Reporter: Brandon Li
>
> Currently truncate is considered as an idempotent call in ClientProtocol. However, the retried RPC request could get a lease error like following:
> 2015-03-12 11:45:47,320 INFO  ipc.Server (Server.java:run(2053)) - IPC Server handler 6 on 8020, call org.apache.hadoop.hdfs.protocol.ClientProtocol.truncate from 192.168.76.4:49763 Call#1 Retry#1: org.apache.hadoop.hdfs.protocol.AlreadyBeingCreatedException: Failed to TRUNCATE_FILE /user/testuser/testFileTr for DFSClient_NONMAPREDUCE_171671673_1 on 192.168.76.4 because DFSClient_NONMAPREDUCE_171671673_1 is already the current lease holder.



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