hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay Radia (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9683) Wrap IpcConnectionContext in RPC headers
Date Thu, 11 Jul 2013 01:02:55 GMT

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

Sanjay Radia commented on HADOOP-9683:
--------------------------------------

Continuing on documenting the offline discussion:
Q> How will multiple sessions be used in the future with the mechanism proposed in this
jira?

A> each session will have its own sasl. i.e. in one connection one will be able to  do
multiple sasl sessions" (in parallel/interleaved).  This can be generalized to cover pipelined
request of multiple capability tokens, such as block tokens, which is needed for each block
access.
Note this feature is not part of this jira but something this jira will enable.

                
> Wrap IpcConnectionContext in RPC headers
> ----------------------------------------
>
>                 Key: HADOOP-9683
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9683
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: ipc
>            Reporter: Luke Lu
>            Assignee: Daryn Sharp
>            Priority: Blocker
>         Attachments: HADOOP-9683.patch
>
>
> After HADOOP-9421, all RPC exchanges (including SASL) are wrapped in RPC headers except
IpcConnectionContext, which is still raw protobuf, which makes request pipelining (a desirable
feature for things like HDFS-2856) impossible to achieve in a backward compatible way. Let's
finish the job and wrap IpcConnectionContext with the RPC request header with the call id
of SET_IPC_CONNECTION_CONTEXT. Or simply make it an optional field in the RPC request header
that gets set for the first RPC call of a given stream.

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