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

Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2013/04/30 04:06:16 UTC

[jira] [Updated] (KAFKA-891) Replica fetcher thread should identify its host,port in the client id

     [ https://issues.apache.org/jira/browse/KAFKA-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Neha Narkhede updated KAFKA-891:
--------------------------------

    Labels: kafka-0.8  (was: )
    
> Replica fetcher thread should identify its host,port in the client id
> ---------------------------------------------------------------------
>
>                 Key: KAFKA-891
>                 URL: https://issues.apache.org/jira/browse/KAFKA-891
>             Project: Kafka
>          Issue Type: Improvement
>          Components: replication
>    Affects Versions: 0.8
>            Reporter: Neha Narkhede
>            Assignee: Neha Narkhede
>            Priority: Critical
>              Labels: kafka-0.8
>
> Replica fetcher thread uses the leader's broker id in the client id that it sets to send requests to the leader. But it is much more convenient to look at the client id and know which replica sent the request to the leader. This is especially important when looking at the request log for troubleshooting replica fetch lag, as an example

--
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