kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kamal Chandraprakash (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5762) Refactor AdminClient to use LogContext
Date Fri, 25 Aug 2017 14:42:01 GMT

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

Kamal Chandraprakash commented on KAFKA-5762:
---------------------------------------------

[~ijuma] Do we have to capture the groupId in the AdminClient ? Or ClientId is enough ?

> Refactor AdminClient to use LogContext
> --------------------------------------
>
>                 Key: KAFKA-5762
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5762
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Ismael Juma
>            Assignee: Kamal Chandraprakash
>
> 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 AdminClient. We should always include the client id.



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

Mime
View raw message