You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2013/10/18 01:56:43 UTC

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

Chris Nauroth created HDFS-5385:
-----------------------------------

             Summary: 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


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)