hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9421) Convert SASL to use ProtoBuf and add lengths for non-blocking processing
Date Fri, 21 Jun 2013 17:31:23 GMT

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

Luke Lu commented on HADOOP-9421:
---------------------------------

bq. Ok, so now how would you handle improved serverId based tokens? Always take the REINITIATE
hit?

Maintain a persistent (serverId -> mech) cache in /tmp/hadoop-$user/rpc. Again: it should
be choice of protocol users (system designers).

bq. In this case, can't the client just blast the INITIATE before getting a NEGOTIATE?

Like I said before, ignoring NEGOTIATE in client increase client complexity to ignore the
right NEGOTIATE. What if server upgrade/security fix happened in between?

bq. do you believe there will actually be a measurable performance difference?

Depending on the use case, e.g. a console managing multiple hadoop clusters in multiple regions:
the additional round trip could be in hundreds of ms! which is extremely annoying.

bq. Will having the client ignore the inflight NEGOTIATE on a reconnect have a measurable
latency

Like I said, client will have to decide when to ignore the NEGOTIATE, which increase client
complexity while still feel dirty. I've shown that this ugliness is not necessary.

bq.  If so, is the extra round trip for REINITIATEs a bad thing

REINITIATE is only supposed to happen when mech cache goes stale.

bq. I'll just add it. I'll re-leverage the existing states to avoid adding the reinitate.

IMO, explicit REINITIATE make things a lot easier to reason about.

bq. prevent a client seizing a connection thread.

What're you talking about? The new protocol allows completely non-blocking client.
                
> 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
>            Priority: Blocker
>         Attachments: HADOOP-9421.patch, HADOOP-9421.patch, HADOOP-9421.patch, HADOOP-9421.patch,
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

Mime
View raw message