[
https://issues.apache.org/jira/browse/HDFS-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706244#comment-13706244
]
Konstantin Shvachko commented on HDFS-4849:
-------------------------------------------
> Is there any reason why this ought to go in before HDFS-4942?
Is there any reason to postpone it any longer?
I don't think we talked about what goes first what goes later. Just that both
make sense.
It's been almost 2 months now with a lot of words exchanged.
I personally still don't understand what is the resistance based on and don't
see why we should not move this forward.
Let's have some action here. I will plan to commit this by the end of the day.
And you know what to do if you feel strongly.
I mean I have things to do other than rewriting the same 30 lines over and over
again.
> 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
