[
https://issues.apache.org/jira/browse/KAFKA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13138614#comment-13138614
]
Jay Kreps commented on KAFKA-168:
---------------------------------
The broker must have an abstract id not tied to host:port, to make it possible
to change the hostname or port or move the data. The consumer id could contain
host (there is no port), though I don't know if this is a good idea.
What I had in mind was just adding this metadata. E.g. programmatically getting
the hostname and adding a rack config parameter and adding this in zk as
metadata.
> 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
