[jira] [Commented] (KAFKA-724) Allow automatic socket.send.buffer from operating system
[ https://issues.apache.org/jira/browse/KAFKA-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559984#comment-13559984 ] Pablo Barrera commented on KAFKA-724: - Apparently this is already fixed in 0.8. > Allow automatic socket.send.buffer from operating system > > > Key: KAFKA-724 > URL: https://issues.apache.org/jira/browse/KAFKA-724 > Project: Kafka > Issue Type: Improvement >Reporter: Pablo Barrera > > To do this, don't call to socket().setXXXBufferSize. This can be > controlled by the configuration parameter: if the value socket.send.buffer or > others are set to -1, don't call to socket().setXXXBufferSize -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KAFKA-724) Allow automatic socket.send.buffer from operating system
Pablo Barrera created KAFKA-724: --- Summary: Allow automatic socket.send.buffer from operating system Key: KAFKA-724 URL: https://issues.apache.org/jira/browse/KAFKA-724 Project: Kafka Issue Type: Improvement Reporter: Pablo Barrera To do this, don't call to socket().setXXXBufferSize. This can be controlled by the configuration parameter: if the value socket.send.buffer or others are set to -1, don't call to socket().setXXXBufferSize -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (KAFKA-687) Rebalance algorithm should consider partitions from all topics
Pablo Barrera created KAFKA-687: --- Summary: Rebalance algorithm should consider partitions from all topics Key: KAFKA-687 URL: https://issues.apache.org/jira/browse/KAFKA-687 Project: Kafka Issue Type: Improvement Reporter: Pablo Barrera The current rebalance step, as stated in the original Kafka paper [1], splits the partitions per topic between all the consumers. So if you have 100 topics with 2 partitions each and 10 consumers only two consumers will be used. That is, for each topic all partitions will be listed and shared between the consumers in the consumer group in order (not randomly). If the consumer group is reading from several topics at the same time it makes sense to split all the partitions from all topics between all the consumer. Following the example, we will have 200 partitions in total, 20 per consumer, using the 10 consumers. The load per topic could be different and the division should consider this. However even a random division should be better than the current algorithm while reading from several topics and should harm reading from a few topics with several partitions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
