[
https://issues.apache.org/jira/browse/HDFS-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Patrick McCabe resolved HDFS-5385.
----------------------------------------
Resolution: Fixed
Fix Version/s: HDFS-4949
> Caching RPCs are AtMostOnce, but do not persist client ID and call ID to edit
> log.
> ----------------------------------------------------------------------------------
>
> Key: HDFS-5385
> URL: https://issues.apache.org/jira/browse/HDFS-5385
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: HDFS-4949
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Fix For: HDFS-4949
>
> Attachments: HDFS-5385.1.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
