hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clint Morgan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4525) config ipc.server.tcpnodelay is no loger being respected
Date Mon, 27 Oct 2008 20:59:44 GMT

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

Clint Morgan commented on HADOOP-4525:

I'm not gonna write a unit test just to make sure a config param is being read, but maybe
someone else wants to. (Making the field final helps a bit here)

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

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

View raw message