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 Tue, 06 Aug 2013 20:56:47 GMT

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

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

bq. I did consider if an exception should be thrown. However, it would preclude the server
sending any control messages to a given session. 
If that is the case then we should enumerate the messages explicitly in the code. 

However, Non-sasl messages will have their own header and will be wrapped - they  will be
parsed by the next layer and the SASL  layer will not see them. If you agree then at this
stage throw the exception.
                
> 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