You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2012/10/01 23:09:07 UTC

[jira] [Commented] (KAFKA-537) expose clientId and correlationId in ConsumerConfig

    [ https://issues.apache.org/jira/browse/KAFKA-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467196#comment-13467196 ] 

Jun Rao commented on KAFKA-537:
-------------------------------

In this jira, we can probably also log the client id when hit unexpected exceptions in the server.
                
> 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
>
>   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