[
https://issues.apache.org/jira/browse/HDFS-9700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347186#comment-15347186
]
Arpit Agarwal commented on HDFS-9700:
-------------------------------------
This is a nice improvement. In the interests of reducing our configuration, are
there any objections to just reusing IPC_CLIENT_TCPNODELAY_DEFAULT instead of
the new config setting DFS_DATA_TRANSFER_CLIENT_TCPNODELAY_KEY (even though
data transfer does not use Hadoop IPC)?
I can't think of a situation where an administrator would want different values
for these settings.
> DFSClient and DFSOutputStream should set TCP_NODELAY on sockets for
> DataTransferProtocol
> ----------------------------------------------------------------------------------------
>
> Key: HDFS-9700
> URL: https://issues.apache.org/jira/browse/HDFS-9700
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs-client
> Affects Versions: 2.7.1, 2.6.3
> Reporter: Gary Helmling
> Assignee: Gary Helmling
> Fix For: 2.8.0
>
> Attachments: HDFS-9700-branch-2.7.002.patch,
> HDFS-9700-branch-2.7.003.patch, HDFS-9700-v1.patch, HDFS-9700-v2.patch,
> HDFS-9700.002.patch, HDFS-9700.003.patch, HDFS-9700.004.patch,
> HDFS-9700_branch-2.7-v2.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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
