[
https://issues.apache.org/jira/browse/HDFS-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705346#comment-13705346
]
Suresh Srinivas commented on HDFS-4849:
---------------------------------------
bq. I thought that at Hadoop Summit we talked about getting the retry cache
done first (HDFS-4942) and doing this later as an optimization. Is there any
reason why this ought to go in before HDFS-4942?
This is how I recall it as well.
bq. Let me know how you want it to be.
Please change idempotent to retry-enabled or some thing like that.
Please see an early patch I have attached to HDFS-4979 on how retry cache looks
like.
> Idempotent create and append operations.
> ----------------------------------------
>
> Key: HDFS-4849
> URL: https://issues.apache.org/jira/browse/HDFS-4849
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 2.0.4-alpha
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Priority: Blocker
> Attachments: idempotentCreate-branch2.patch, idempotentCreate.patch,
> idempotentCreate.patch, idempotentCreate.patch, idempotentCreate.patch
>
>
> create, append and delete operations can be made idempotent. This will reduce
> chances for a job or other app failures when NN fails over.
--
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
