[
https://issues.apache.org/jira/browse/KUDU-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-1907:
------------------------------
Priority: Minor (was: Major)
> Lock contention in SASL Kerberos negotiation
> --------------------------------------------
>
> Key: KUDU-1907
> URL: https://issues.apache.org/jira/browse/KUDU-1907
> Project: Kudu
> Issue Type: Bug
> Components: perf, rpc
> Affects Versions: 1.3.0
> Reporter: Todd Lipcon
> Priority: Minor
>
> Dan wrote a negotiation benchmark and found that we can only do ~600 kerberos
> negotiations/second regardless of the number of concurrent clients. Looking
> at stack traces reveals that the SASL GSSAPI plugin adds locks around all
> GSSAPI calls, though it seems like the underlying GSSAPI library is actually
> thread-safe. (the locks are a relic from bygone days).
> Given that we are only using a small sliver of Cyrus-SASL functionality, we
> should consider using libgssapi directly instead of via SASL.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
