[
https://issues.apache.org/jira/browse/HADOOP-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679738#comment-13679738
]
Luke Lu commented on HADOOP-9421:
---------------------------------
bq. Shorting out the NEGOTIATE for a re-connect becomes a bit complicated. The
connection header doesn't contain a length like other RPC packets
You can always send the length + RpcSaslProto after the fixed connection
header. Server can than send the appropriate challenge or negotiate
accordingly. It seems more straight forward than the alternatives here.
bq. the only way to signal the server is another authProtocol to not send a
NEGOTIATE,
It's not the only way (see above). But it could work, which is the saving grace
of AuthProtocol :) though SASL2 or HSASL (pronounced as hassle) and its variant
is kinda ugly.
bq. The client needs the server's NEGOTIATE to correctly instantiate its SASL
client. This negates the ability for the client to cache values for an
immediate INITIATE.
That's why it's called "cached" initiation, server can always send NEGOTIATE as
it see fit after fail over. This is also why I prefer always sending
RpcSaslProto first, so server can decide what to respond in a straight forward
way. Fail over handling is not a common workload, the goal of client cached
initiation is to reduce server side processing in common cases like
container/task launching, when NN/RM are not failing over left and right.
Anyway, though I'm not too happy with the evolution via AuthProtocol approach.
I think I can live with it.
> 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
