hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10564) Add username to native RPCv9 client
Date Mon, 12 May 2014 19:37:17 GMT

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

Colin Patrick McCabe updated HADOOP-10564:

    Attachment: HADOOP-10564-pnative.005.patch

Hi Binglin, 

Earlier, on HADOOP-10389, you made a comment that we should set call id rather than just using
0 everywhere.  I implemented this in version #5 of this patch.

I think the comment was this:

bq. 1. to my understanding, rpc client should have a map<callid, call> to record all
unfinished calls, but I could not find any code assigning callids(only make them 0) and manage
unfinished calls, could you help me located those logic?

We don't need a map here, since we can only have one call ID in flight at once (the server
doesn't *yet* support this).  In the future, this might change, but for now, it's OK just
to check that the call ID we got in the response was the same as the call ID we made in the

> Add username to native RPCv9 client
> -----------------------------------
>                 Key: HADOOP-10564
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10564
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: native
>    Affects Versions: HADOOP-10388
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>         Attachments: HADOOP-10564-pnative.002.patch, HADOOP-10564-pnative.003.patch,
HADOOP-10564-pnative.004.patch, HADOOP-10564-pnative.005.patch, HADOOP-10564.001.patch
> Add the ability for the native RPCv9 client to set a username when initiating a connection.

This message was sent by Atlassian JIRA

View raw message