[
https://issues.apache.org/jira/browse/HADOOP-9820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732137#comment-13732137
]
Sanjay Radia commented on HADOOP-9820:
--------------------------------------
The RPC header and the SASL header after the it (but before the wrapped data)
are not wrapped. The wrapped reply also has unwrapped headers (RPC and SASL).
So the exception (if say the RPC header or the SASL is incorrect) will pass
through fine. Indeed that is the beauty of the headers to the wrapped data - it
does allow throwing an exception at the outer layer. The only problem is that
if there is an exception at the RPC layer (above the wrapped layer) then the
client has to be able to unwrap in order to read 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
