[
https://issues.apache.org/jira/browse/HADOOP-9820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732103#comment-13732103
]
Daryn Sharp commented on HADOOP-9820:
-------------------------------------
Currently, yes, all RPC packets are wrapped and processed on the other side
after unwrapping. Therein lies the possible problem with sending control
messages.
Let's say we do throw an exception as suggested. If the server cannot unwrap
the SASL data, the client unlikely to be able to unwrap. The server would need
to send a non-wrapped exception response to notify the client that wrapping
isn't working, which this patch allows.
Perhaps a better approach is to only allow out-of-band RPC (negative callIds)
to be sent unwrapped over a wrapped stream?
> 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
