hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Li (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-7925) truncate RPC should not be considered as idempotent
Date Thu, 12 Mar 2015 23:42:40 GMT

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

Brandon Li updated HDFS-7925:
-----------------------------
    Summary: truncate RPC should not be considered as idempotent  (was: truncate RPC should
not be considered idempotent)

> 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/hrt_qa/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)

Mime
View raw message