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

ASF GitHub Bot commented on KAFKA-3278:
---------------------------------------

GitHub user tomdearman opened a pull request:

    https://github.com/apache/kafka/pull/978

    KAFKA-3278 concatenate thread name to clientId when producer and consumers 
config is created

    @guozhangwang made the changes as requested, I reverted my original commit 
and that seems to have closed the other pull request - sorry if that mucks up 
the process a bit

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tomdearman/kafka KAFKA-3278

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/978.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #978
    
----
commit 172230a76033d22ed9712fa55f454d32fa37286b
Author: tomdearman <tom.dear...@gmail.com>
Date:   2016-02-26T10:32:05Z

    KAFKA-3278 concatenate thread name to clientId when producer and consumers 
config is created

----


> clientId is not unique in producer/consumer registration leads to mbean 
> warning
> -------------------------------------------------------------------------------
>
>                 Key: KAFKA-3278
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3278
>             Project: Kafka
>          Issue Type: Bug
>          Components: kafka streams
>    Affects Versions: 0.9.0.1
>         Environment: Mac OS
>            Reporter: Tom Dearman
>            Assignee: Tom Dearman
>            Priority: Minor
>             Fix For: 0.10.0.0
>
>
> The clientId passed through to StreamThread is not unique and this is used to 
> create consumers and producers, which in turn try to register mbeans, this 
> leads to a warn that mbean already registered.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to