hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Helmling (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-9805) TCP_NODELAY not set before SASL handshake in data transfer pipeline
Date Mon, 27 Jun 2016 17:37:52 GMT

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

Gary Helmling updated HDFS-9805:
    Attachment: HDFS-9805.004.patch

Updated patch adding:

* a new configuration property (dfs.data.transfer.server.tcpnodelay), defaulting to true,
controlling the TCP_NODELAY setting in the DN -> DN transfer path
* a test case check the TCP_NODELAY was enabled on all used sockets when the relevant config
settings are enabled

Note that I had to modify {{DataNode#newSocket()}} in this patch in order to support the test
case.  Prior to this, {{newSocket()}} was not using the configured socket factory, instead
creating sockets directly.  This seems like a change we would want anyway, just calling in

> TCP_NODELAY not set before SASL handshake in data transfer pipeline
> -------------------------------------------------------------------
>                 Key: HDFS-9805
>                 URL: https://issues.apache.org/jira/browse/HDFS-9805
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>            Reporter: Gary Helmling
>            Assignee: Gary Helmling
>         Attachments: HDFS-9805.002.patch, HDFS-9805.003.patch, HDFS-9805.004.patch
> There are a few places in the DN -> DN block transfer pipeline where TCP_NODELAY is
not set before doing a SASL handshake:
> * in {{DataNode.DataTransfer::run()}}
> * in {{DataXceiver::replaceBlock()}}
> * in {{DataXceiver::writeBlock()}}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message