hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9421) Convert SASL to use ProtoBuf and add lengths for non-blocking processing
Date Mon, 10 Jun 2013 20:30:21 GMT

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

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

bq.  This optimizes a reconnect, but the common case of initial connect will now take an additional
round trip penalty by sending a second message to request the NEGOTIATE.

No, for common case, server can detect that client selected the correct mechanism (note RpcSaslProto
is extensible to contain the appropriate metadata needed for server to verify) and respond
with a normal sasl challenge (again extensible to contain server principal) instead of negotiate.
So my proposal actually works with majority of failover case (the mechanism doesn't change
besides server name etc.) with no additional round trip as well. 
  
                
> 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.patch, HADOOP-9421.patch, 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

Mime
View raw message