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

Luke Lu commented on HADOOP-9421:
---------------------------------

bq. When it gets an RPC error, such as invalid rpc version or unsupported 
serialization, it blows up trying to decode it as SASL.

The server should reply with client version appropriate response, see 
Server#setupBadVersionResponse, which currently doesn't handle sasl correctly 
for >=9 case, because the code not finished yet :). But this is a separate 
issue. Stuffing SASL exchange in RpcRequestHeaderProto seems to be hack to me 
to avoid fixing the bad version response. 
                
> Convert SASL to use ProtoBuf and add lengths for non-blocking processing
> ------------------------------------------------------------------------
>
>                 Key: HADOOP-9421
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9421
>             Project: Hadoop Common
>          Issue Type: Sub-task
>    Affects Versions: 2.0.3-alpha
>            Reporter: Sanjay Radia
>            Assignee: Daryn Sharp
>         Attachments: HADOOP-9421.patch, HADOOP-9421-v2-demo.patch
>
>


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

Reply via email to