hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8069) Enable TCP_NODELAY by default for IPC
Date Thu, 16 Feb 2012 07:17:04 GMT

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

Suresh Srinivas commented on HADOOP-8069:

bq. ... cross the 8K boundary would be getListing()
This is what I was thinking. However we have iterative listing now. With that perhaps the
probability of such RPCs > 8K is lower. However we should tweek DFS_LIST_LIMIT_DEFAULT,
certainly based on your findings.

Additionally there are other RPCs such as Namenode#getBlocks(), ClientProtocol#listCorruptBlocks().
However these are not frequently called.

> 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
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message