[
https://issues.apache.org/jira/browse/KAFKA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134270#comment-13134270
]
Jay Kreps commented on KAFKA-168:
---------------------------------
Ideally we would also support rack locality in the partition assignment so that
the brokers would have both a hostname and a rack name in their config. We
would prefer partitions from an identical host, then from the same rack, then
any partition.
> Support locality in consumer partition assignment algorithm
> -----------------------------------------------------------
>
> Key: KAFKA-168
> URL: https://issues.apache.org/jira/browse/KAFKA-168
> Project: Kafka
> Issue Type: New Feature
> Components: core
> Reporter: Jay Kreps
>
> There are some use-cases where it makes sense to co-locate brokers and
> consumer processes. In this case it would be nice to optimize the assignment
> of partitions to consumers so that the consumer preferentially consumes from
> the broker with which it is co-located.
> If we are going to do KAFKA-167, moving the assignment to the broker, it
> would make sense to do that first so we only have to change the logic in one
> place.
--
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
