[HDFS-7925] truncate RPC should not be considered as idempotent

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.7.0
• Component/s: namenode
• Assignee: Unassigned
• Reporter: Brandon Li
• Created: 12/Mar/15 23:42
• Updated: 13/Mar/15 03:04
• Resolved: 13/Mar/15 03:04

Description

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.