[HDFS-5385] Caching RPCs are AtMostOnce, but do not persist client ID and call ID to edit log.

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: HDFS-4949
• Fix Version/s: HDFS-4949
• Component/s: namenode
• Target Version/s: HDFS-4949
• Assignee: Chris Nauroth
• Reporter: Chris Nauroth
• Created: 17/Oct/13 23:55
• Updated: 21/Oct/13 19:49
• Resolved: 21/Oct/13 19:42

Description

All of the new caching RPCs defined on ClientProtocol are annotated @AtMostOnce. However, their underlying edit log operations do not persist the RPC client ID and call ID. In the event of an HA failover, the new primary will not be able to guarantee at-most-once semantics if the clients retry.

Issue Links

• relates to: HDFS-4949 Centralized cache management in HDFS