[
https://issues.apache.org/jira/browse/HADOOP-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679842#comment-13679842
]
Daryn Sharp commented on HADOOP-9421:
-------------------------------------
I believe you are proposing the client always sends two messages upon connect:
the connect header and a SASL INITIATE. 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. To allow for IP
failover, I guess that means the server response to an invalid INITIATE is a
NEGOTIATE instead of returning authentication failed and closing the
connection? Presumably the second bad INITIATE will continue to return auth
failed?
I'm unclear what the next step is for this patch. I'm not too happy about
evolution via AuthProtocol either but it's the only way I can think of to avoid
penalizing the initial connect with another roundtrip. By saying you can live
with it, is that a tacit +1 or do you want further changes to this patch?
> 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
