kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jay Kreps (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-200) Support configurable send / receive socket buffer size in server
Date Tue, 13 Dec 2011 18:38:30 GMT

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

Jay Kreps commented on KAFKA-200:

Interesting. Can we validate the setting directly by checking getReceiveBufferSize()?

I think the reason it may be working is that linux defaults tcp window scaling on...I think
the current approach would not work on Solaris because it defaults tcp window scaling off.
Or maybe I am wrong. But I think we would be better off doing it the way they recommend and
setting the buffer size in the way the documentation encourages.
> Support configurable send / receive socket buffer size in server
> ----------------------------------------------------------------
>                 Key: KAFKA-200
>                 URL: https://issues.apache.org/jira/browse/KAFKA-200
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.7
>            Reporter: John Fung
>             Fix For: 0.8
>         Attachments: KAFKA-200.patch
> * Make the send / receive socket buffer size configurable in server.
> * KafkaConfig.scala already has the following existing variables to support send / receive
>     socketSendBuffer
>     socketReceiveBuffer
> * The patch attached to this ticket will read the following existing settings in <kafka>/config/server.properties
and set the corresponding socket buffers
>     . . .
>     # The send buffer (SO_SNDBUF) used by the socket server
>     socket.send.buffer=1048576
>     # The receive buffer (SO_RCVBUF) used by the socket server
>     socket.receive.buffer=1048576

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