[
https://issues.apache.org/jira/browse/KAFKA-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942633#comment-13942633
]
Neha Narkhede commented on KAFKA-891:
-------------------------------------
Right, the idea of client id is to identify the application. In this case, it
is the replica that sends fetch requests to the leader. The question is what is
the best way to identify a replica? It can either be the replica's brokerid or
host and port. That is what I filed the JIRA for. Currently, the logs are still
unreadable since the replicas identify themselves as replica-<leader_id>. So it
is difficult to tell one replica from the other :)
> 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.0
> 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 was sent by Atlassian JIRA
(v6.2#6252)
