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

Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2017/09/11 14:50:00 UTC

[jira] [Resolved] (KAFKA-5763) Refactor NetworkClient to use LogContext

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

Ismael Juma resolved KAFKA-5763.
--------------------------------
    Resolution: Fixed

> Refactor NetworkClient to use LogContext
> ----------------------------------------
>
>                 Key: KAFKA-5763
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5763
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Ismael Juma
>             Fix For: 1.0.0
>
>
> We added a LogContext object which automatically adds a log prefix to every message written by loggers constructed from it (much like the Logging mixin available in the server code). We use this in the consumer to ensure that messages always contain the consumer group and client ids, which is very helpful when multiple consumers are run on the same instance. We should do something similar for the NetworkClient. We should always include the client id.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)