[
https://issues.apache.org/jira/browse/HDFS-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713444#comment-13713444
]
Suresh Srinivas edited comment on HDFS-4974 at 7/19/13 8:37 AM:
----------------------------------------------------------------
Made the following changes in this early patch:
# I added a new annotation "AtMostOnce" to annotate the methods that guarantee
the "at-most-once" semantics. That is the server-side executes these methods
only once using retry cache functionality.
# I have added annotations to all the methods in protocols implemented by the
namenode.
# Also added a test to ensure we check for these annotations. This will ensure
future protocol changes where someone might miss adding the annotation.
was (Author: sureshms):
Made following changes in this early patch:
# I added a new annotation "AtMostOnce" to annotate the methods that guarantee
the "at-most-once" semantics. That is the server-side executes these methods
only once using retry cache functionality.
# I have added annotations to all the methods in protocols implemented by the
namenode.
# Also added a test to ensure we check for these annotations. This will ensure
future protocol changes where someone might miss adding the annotation.
> Analyze and add annotations to Namenode and Datanode protocol methods to
> enable retry
> -------------------------------------------------------------------------------------
>
> Key: HDFS-4974
> URL: https://issues.apache.org/jira/browse/HDFS-4974
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, namenode
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Attachments: HDFS-4974.patch
>
>
> This jira is intended for:
> # Discussing current @Idempotent annotations in HDFS protocols and adding
> that annotation where it is missing.
> # Discuss how retry should be enabled for non-idempotent requests.
> I will post the analysis of current methods in a subsequent comment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
