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 "Chris Douglas (JIRA)" <ji...@apache.org> on 2008/10/28 00:11:45 UTC

[jira] Issue Comment Edited: (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=12643092#action_12643092 ] 

chris.douglas edited comment on HADOOP-4525 at 10/27/08 4:10 PM:
-----------------------------------------------------------------

This was my fault. HADOOP-2645 knocked the patch for HADOOP-2232 out of sync and I must not have noticed when applying it. Apologies.

I don't think this needs a unit test.

      was (Author: chris.douglas):
    This was my fault. HADOOP-2643 knocked the patch for HADOOP-2232 out of sync and I must not have noticed when applying it. Apologies.

I don't think this needs a unit test.
  
> 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.