You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Dan Burkert (JIRA)" <ji...@apache.org> on 2017/03/03 22:11:45 UTC

[jira] [Updated] (KUDU-1897) GSSAPI negotiation single-threaded and very slow under concurrency

     [ https://issues.apache.org/jira/browse/KUDU-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Burkert updated KUDU-1897:
------------------------------
    Status: In Review  (was: In Progress)

> GSSAPI negotiation single-threaded and very slow under concurrency
> ------------------------------------------------------------------
>
>                 Key: KUDU-1897
>                 URL: https://issues.apache.org/jira/browse/KUDU-1897
>             Project: Kudu
>          Issue Type: Bug
>          Components: rpc, security
>    Affects Versions: 1.3.0
>            Reporter: Todd Lipcon
>            Assignee: Dan Burkert
>            Priority: Critical
>         Attachments: rcache.png
>
>
> I'm running an Impala workload with ~10 concurrent clients submitting queries that take a few seconds each on a 9 node cluster. The master is pegging on core in negotiation, and has a bunch of other negotiation threads blocked on a mutex within SASL.
> Each negotiation is taking 2-3 seconds due to waiting on this lock.
> This severely restricts connection throughput, and probably needs to be addressed for 1.3.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)