[
https://issues.apache.org/jira/browse/HADOOP-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643063#action_12643063
]
Raghu Angadi commented on HADOOP-4525:
--------------------------------------
> I don't know how you say "it does not look like the this config is was ever
> read by the server." It was at least being read in the patch that first
> introduced it: HADOOP-2232
For some reason, it was not committed properly :
http://svn.apache.org/viewvc/hadoop/core/branches/branch-0.16/src/java/org/apache/hadoop/ipc/Server.java?r1=615093&r2=615098
i.e. committed patch does not read this config.
> config ipc.server.tcpnodelay is no loger being respected
> --------------------------------------------------------
>
> Key: HADOOP-4525
> URL: https://issues.apache.org/jira/browse/HADOOP-4525
> Project: Hadoop Core
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.18.1
> Reporter: Clint Morgan
> Attachments: hadoop-4525.patch
>
>
> I was troubleshooting some slow IPC from hbase, and though it may be a
> Naggles algorithm issue. So I turned on tcpNoDelay on the client and server
> and this had no affect. Turns out that the "ipc.server.tcpnodelay" setting
> was no longer being read.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
