[
https://issues.apache.org/jira/browse/HADOOP-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679663#comment-13679663
]
Daryn Sharp commented on HADOOP-9421:
-------------------------------------
Shorting out the NEGOTIATE for a re-connect becomes a bit complicated. The
connection header doesn't contain a length like other RPC packets, so about the
only way to signal the server is another authProtocol to not send a NEGOTIATE,
but expect a subsequent INITIATE. As discussed earlier, I'd prefer to defer
the reconnect optimization to a followup jira.
BTW, I'm currently working on IP failover. We're blocked on HA deployment
because we can't manage the logistics of updating confs and restarting every
cluster & services like oozie and hdfsproxy, etc when one cluster is HA enabled
or its HA config changes. IP failover is the answer but that's blocked too
because the service principal changes when failover occurs. 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. The IP
failover work is based upon this jira.
bq. Though DIGEST is not exactly a precise word here, TOKEN is, IMO, even more
nebulous. How about CHALLENGE_RESPONSE or simply CR? I'd prefer the rename to
be in separate JIRA as well, as it doesn't really affect the wire protocol.
Actually, it does affect the wire because that is a value passed over the wire.
Ie. "TOKEN" via "DIGEST-MD5", or "TOKEN" via "SCRAM", etc.
> 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
