You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "TAO XIAO (JIRA)" <ji...@apache.org> on 2017/07/06 01:53:01 UTC

[jira] [Commented] (KAFKA-5559) Metrics should throw if two client registers with same ID

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

TAO XIAO commented on KAFKA-5559:
---------------------------------

Does this PR suggest we need to use different {{client.id}} with multi-threading in the same JVM? As per my understanding (up to 0.10.0.0) {{client.id}} is the one that is used to identify an application when enabling quota. If this is case how do we have a model that have multiple consumers in the same JVM that share the same quota? 

Also there are many streaming frameworks, e.g. Storm, Flink, bootstrapping multiple consumers in the same JVM when working with local mode (especially useful for development and debugging purpose), how do we cope with this situation as well? 

> Metrics should throw if two client registers with same ID
> ---------------------------------------------------------
>
>                 Key: KAFKA-5559
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5559
>             Project: Kafka
>          Issue Type: Bug
>          Components: metrics
>    Affects Versions: 0.11.0.0
>            Reporter: Matthias J. Sax
>            Assignee: Matthias J. Sax
>
> Currently, {{AppInfoParser}} only logs a WARN message when a bean is registered with an existing name. However, this should be treated as an error and the exception should be rthrown.



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