You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Raghu Angadi (JIRA)" <ji...@apache.org> on 2008/10/27 21:39:44 UTC

[jira] Commented: (HADOOP-4525) config ipc.server.tcpnodelay is no loger being respected

    [ https://issues.apache.org/jira/browse/HADOOP-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643046#action_12643046 ] 

Raghu Angadi commented on HADOOP-4525:
--------------------------------------

Can we have a unit test for this? Since this is a performance problem, it won't be detected next time something like this happens.

> 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.