[
https://issues.apache.org/jira/browse/HADOOP-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077787#comment-14077787
]
Hudson commented on HADOOP-8069:
--------------------------------
SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1846 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1846/])
HADOOP-8069. Enable TCP_NODELAY by default for IPC. (Contributed by Todd
Lipcon) (arp:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1614242)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/CommonConfigurationKeysPublic.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/resources/core-default.xml
> Enable TCP_NODELAY by default for IPC
> -------------------------------------
>
> Key: HADOOP-8069
> URL: https://issues.apache.org/jira/browse/HADOOP-8069
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Affects Versions: 0.23.0, 2.4.1
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 3.0.0, 2.6.0
>
> Attachments: hadoop-8069.txt
>
>
> I think we should switch the default for the IPC client and server NODELAY
> options to true. As wikipedia says:
> {quote}
> In general, since Nagle's algorithm is only a defense against careless
> applications, it will not benefit a carefully written application that takes
> proper care of buffering; the algorithm has either no effect, or negative
> effect on the application.
> {quote}
> Since our IPC layer is well contained and does its own buffering, we
> shouldn't be careless.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
