hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9688) Add globally unique Client ID to RPC requests
Date Wed, 10 Jul 2013 20:53:49 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-9688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705049#comment-13705049

Konstantin Shvachko commented on HADOOP-9688:

Should we then eliminate DFSClient.clientName and make DFSClient.getClientName() return Client.uuid?

> I think randomUUID collision probability is very low. If not better, it should not be
worse than storageID.

storageIDs are unique. There is now probability they will collide as far as I remember. I
am saying we can do the same for clientID. 
You know in big clusters most improbable events happen all the time.
Yes, I read all the comments.
> Add globally unique Client ID to RPC requests
> ---------------------------------------------
>                 Key: HADOOP-9688
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9688
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>            Priority: Blocker
>             Fix For: 3.0.0
>         Attachments: HADOOP-9688.clientId.1.patch, HADOOP-9688.clientId.patch, HADOOP-9688.patch
> This is a subtask in hadoop-common related to HDFS-4942 to add unique request ID to RPC

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

View raw message