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] [Commented] (HADOOP-9716) Move the Rpc request call ID generation to client side InvocationHandler
Date Mon, 15 Jul 2013 00:54:49 GMT

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

Suresh Srinivas commented on HADOOP-9716:
-----------------------------------------

bq. So, should we just add it here?
Do you mean add it to the response? Currently in Rpc response I did not add the client Id.
But adding retry count to the response, which is not expensive (1 byte cost), even though
may not be used right now, may be okay. 
                
> Move the Rpc request call ID generation to client side InvocationHandler
> ------------------------------------------------------------------------
>
>                 Key: HADOOP-9716
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9716
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Suresh Srinivas
>            Assignee: Tsz Wo (Nicholas), SZE
>         Attachments: c9716_20130712b.patch, c9716_20130712.patch, c9716_20130713b.patch,
c9716_20130713c.patch, c9716_20130713.patch
>
>
> Currently when RetryInvocationHandler is used to retry an RPC request, a new RPC request
call ID is generated. This jira proposes moving call ID generation to InvocationHandler so
that retried RPC requests retain the same call ID. This is needed for RetryCache functionality
proposed in HDFS-4942.

--
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

Mime
View raw message