[
https://issues.apache.org/jira/browse/KAFKA-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473835#comment-13473835
]
Yang Ye commented on KAFKA-537:
-------------------------------
To enable special consumer to fetch from any replica, we don't use client id,
we use the replicaId in the fetch request. (-1 means from ordinary consumer, -2
from low level consumer (that can fetch from any replica, n>=0 means from
broker n)
Client id is currently used for identify each difference service. (client of
kafka)
correlation id is currently not used. We can discuss how to use it tmr
> expose clientId and correlationId in ConsumerConfig
> ---------------------------------------------------
>
> Key: KAFKA-537
> URL: https://issues.apache.org/jira/browse/KAFKA-537
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Yang Ye
> Labels: bugs, newbie
> Fix For: 0.8
>
> Attachments: kafka_537_v1.diff
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> We need to expose clientId and correlationId in ConsumerConfig and use it
> properly in AbstractFetcherThread. For follower fetchers, we should set the
> clientId to a special string, something list "follower".
--
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
