[
https://issues.apache.org/jira/browse/HDFS-9700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123206#comment-15123206
]
Masatake Iwasaki commented on HDFS-9700:
----------------------------------------
{{CommonConfigurationKeysPublic.IPC_CLIENT_TCPNODELAY_KEY}} is configuration
key for Hadoop IPC but the sockets refered here are for data transfer protocol
(which does not use common IPC framework). Should we use another key or always
set TCP_NODELAY as {{DFSUtilClient#peerFromSocket}} do, if it is crucial?
> DFSClient and DFSOutputStream do not respect TCP_NODELAY config in two spots
> ----------------------------------------------------------------------------
>
> Key: HDFS-9700
> URL: https://issues.apache.org/jira/browse/HDFS-9700
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Affects Versions: 2.7.1, 2.6.3
> Reporter: Gary Helmling
> Assignee: Gary Helmling
> Attachments: HDFS-9700-v1.patch, HDFS-9700_branch-2.7.patch
>
>
> In {{DFSClient.connectToDN()}} and
> {{DFSOutputStream.createSocketForPipeline()}}, we never call
> {{setTcpNoDelay()}} on the constructed socket before sending. In both cases,
> we should respect the value of ipc.client.tcpnodelay in the configuration.
> While this applies whether security is enabled or not, it seems to have a
> bigger impact on latency when security is enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
