hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9421) Add full length to SASL response to allow non-blocking readers
Date Fri, 12 Apr 2013 20:18:16 GMT

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

Daryn Sharp commented on HADOOP-9421:

I'd also like to include my idea (I think it's in another jira somewhere...) of the server
TELLING the client the service of the token it wants, instead of the client trying to "guess"
the token beforehand.  The server should provide an opaque id and the client just tries to
look it up.

This would remove the growing mess associated with clients juggling hostnames vs. IP addrs
vs. HA logical names.  Decoupling the lookup of a token from its issuing host or IP, and using
a server specified identifier removes current limitations on being able to support multiple
NICs (client gets token over public iface 1, nodes can't use token via internal iface 2),
support tokens acquired through NAT, and sharable tokens between HA NNs w/o any custom client-side
> Add full length to SASL response to allow non-blocking readers
> --------------------------------------------------------------
>                 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: Junping Du
>         Attachments: HADOOP-9421.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

View raw message