[HDFS-7926] NameNode implementation of ClientProtocol.truncate(..) is not idempotent

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.7.0
• Component/s: namenode
• Target Version/s: 2.7.0
• Hadoop Flags: Reviewed
• Assignee: Tsz-wo Sze
• Reporter: Tsz-wo Sze
• Created: 13/Mar/15 01:06
• Updated: 14/Nov/21 08:53
• Resolved: 13/Mar/15 18:28

Description

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.

Issue Links

• relates to: HDFS-16322 The NameNode implementation of ClientProtocol.truncate(...) can cause data loss.