[
https://issues.apache.org/jira/browse/HDFS-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410463#comment-16410463
]
Hudson commented on HDFS-11767:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13869 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13869/])
HDFS-11767: libhdfs++: SASL events should be scoped closer to usage.
(james.clampffer: rev 57cdad73deecdb39fbe3c43688dbd71bcfd0e31a)
* (edit)
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/rpc/sasl_protocol.h
* (edit)
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/rpc/sasl_protocol.cc
> libhdfs++: SASL events should be scoped closer to usage
> -------------------------------------------------------
>
> Key: HDFS-11767
> URL: https://issues.apache.org/jira/browse/HDFS-11767
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: James Clampffer
> Assignee: James Clampffer
> Priority: Major
> Attachments: HDFS-11767.HDFS-8707.000.patch
>
>
> "SASL Start" and "SASL End" are called in the SaslProtocol constructor and
> destructor. SaslProtocol is held by a shared_ptr so there's a race where the
> RpcConnection can be torn down and another can be put in it's place while a
> callback is still holding the shared_ptr preventing "SASL End" from being
> called.
> This can matter a lot because both Cyrus SASL and gsasl aren't thread safe
> during negotiation. These event hooks provide a mechanism to pick up a
> process wide lock that guards access to the sasl library.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
