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 Wed, 24 Apr 2013 21:51:16 GMT

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

Daryn Sharp commented on HADOOP-9421:
-------------------------------------

bq. Again, client can cache the server mechanisms and associated info, which almost never
change across connections.

OTOH, RPC connections are already cached and multiplex multiple high level clients.  It's
a premature optimization to introduce extra complexity to remove one RPC for reconnects. 
I'd suggest we narrow the scope of this jira to the basic design, and we may later consider
this optimization on another jira.

bq. My point is that using sasl-next

In my prior comment, I abandoned it and proposed a hybrid compromise.  What are your thoughts
on that?
                
> 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

Mime
View raw message