[
https://issues.apache.org/jira/browse/HDFS-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688322#comment-13688322
]
Konstantin Shvachko commented on HDFS-4849:
-------------------------------------------
Vinod, DFSClient gets its name from MapReduce via "mapreduce.task.attempt.id"
config parameter. It becomes a part of the clientName. Since attempt ids are
unique (modular certain failure scenarios) the clients have unique names as
well. You don't need ZK to generate UUIDs.
As I said before HDFS can and should provide unique clientNames for non MR
apps. Will open a jira for that.
> 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.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
