[
https://issues.apache.org/jira/browse/HDFS-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200202#comment-14200202
]
Hudson commented on HDFS-7367:
------------------------------
SUCCESS: Integrated in Hadoop-Hdfs-trunk #1925 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1925/])
HDFS-7367. HDFS short-circuit read cannot negotiate shared memory slot and file
descriptors when SASL is enabled on DataTransferProtocol. Contributed by Chris
Nauroth. (wheat9: rev 8e33d4bdb35eed8b60cf197247fad465b1912ef7)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/datatransfer/sasl/SaslDataTransferServer.java
> HDFS short-circuit read cannot negotiate shared memory slot and file
> descriptors when SASL is enabled on DataTransferProtocol.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-7367
> URL: https://issues.apache.org/jira/browse/HDFS-7367
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Fix For: 2.6.0
>
> Attachments: HDFS-7367.1.patch
>
>
> When both short-circuit read and SASL on DataTransferProtocol are enabled,
> the server side tries to negotiate SASL on the operation to allocate a new
> shared memory slot. However, the transport for this operation is the Unix
> domain socket (not TCP), and the client always assumes that Unix domain
> socket traffic is trustworthy. The end result is that the server side still
> attempts SASL negotiation, and it fails with an exception while erroneously
> trying to parse the domain socket address as if it were a network address.
> The read succeeds, but only because we fallback to a read through the
> DataNode TCP server. It's not a short-circuit read.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
