hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-9688) Add globally unique request ID to RPC requests
Date Wed, 03 Jul 2013 00:05:20 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-9688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Suresh Srinivas updated HADOOP-9688:

    Attachment: HADOOP-9688.patch

Here is an early patch. Several things that we should still discuss:
# RPC request callID essentially has become a sequence number. Should we change the field
name to sequence number?
# RPC request field requestID currently is not sent in response. For a client call ID is unique
enough to map the response to a corresponding request. Do we need to add requestID in response
also? I do not see the need.
# For SaslRpcClient I am seeting the request ID to empty byte array, because retry is not
expected for this and this request will not be handled by RPC server implementation. Does
this look right?
# Also I want to call out attendtion to - this change adds UUID for all RPC requests, irrespective
of if an RPC server implementation handles retransmits or not. Optimizing this out seems unnecessary.

> Add globally unique request 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
>         Attachments: 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