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-9820) RPCv9 wire protocol is insufficient to support multiplexing
Date Wed, 07 Aug 2013 16:48:54 GMT

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

Sanjay Radia commented on HADOOP-9820:
--------------------------------------

bq. Let's say we do throw an exception as suggested.  If the server cannot unwrap the SASL
data, ...
Note the exception is not being thrown because the server cannot unwrap, the exception is
being thrown because *currently* the only header that is acceptable when wrapping is enabled
is the RPC-header-callId=sasl *with* the SASL-state=wrapped header. If you don't get that
then throw the exception (which will go with its own response header). Later when we add multiplexing
we will allow RPC-header-callId=sasl *with* start new rpc-stream and here comes its its SASL-authenticate
exchange.
                
> RPCv9 wire protocol is insufficient to support multiplexing
> -----------------------------------------------------------
>
>                 Key: HADOOP-9820
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9820
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc, security
>    Affects Versions: 3.0.0, 2.1.0-beta
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>         Attachments: HADOOP-9820.patch
>
>
> RPCv9 is intended to allow future support of multiplexing.  This requires all wire messages
to be tagged with a RPC header so a demux can decode and route the messages accordingly.
> RPC ping packets and SASL QOP wrapped data is known to not be tagged with a header.

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