[
https://issues.apache.org/jira/browse/KAFKA-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472678#comment-13472678
]
Jay Kreps commented on KAFKA-537:
---------------------------------
The correlation id is meant to be a per-connection, per-client, per-request
counter. This lets the client have multiple in-flight requests at the same time
on the same connection. So it should not be exposed in the client config as a
static value. Instead we should initialize an AtomicInteger to 0 and pass in
counter.getAndIncrement() to the request on each call.
> 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
> 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
