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 Thu, 08 Aug 2013 00:00:49 GMT

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

Sanjay Radia commented on HADOOP-9820:

bq. The more specific cases I had in mind: ...  Server wants to send a non-sensitive control
messages like "is session alive" or "close session". Requiring non-sensitive messages to be
wrapped/unwrapped seems overkill.

I am in agreement with you here. But I was never proposing that we need to wrap such stuff
in the future. Since you are responding to an issue I never raised, perhaps you are misreading
my concern.
All I am just saying: in  SaslRpcClient#SaslRpcInputStream.readNextRpcPacket line 569:
    if (headerBuilder.getCallId() != AuthProtocol.SASL.callId) {...
     throw an exception, perhaps close the connection with fatal exception
In the future when we have out-of-band messages we can enumerate the ones that are allowed.

> 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

View raw message