[
https://issues.apache.org/jira/browse/KAFKA-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-891.
-----------------------------
Resolution: Fixed
The idea of the client id is really to identify an application. The host/port
should be available in the server from the connection, right?
> 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)
