You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/11/10 19:56:11 UTC
[jira] [Commented] (KAFKA-2798) Kafka Connect distributed configs
can conflict with producer/consumer configs, making it impossible to
control them independently
[ https://issues.apache.org/jira/browse/KAFKA-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999114#comment-14999114 ]
ASF GitHub Bot commented on KAFKA-2798:
---------------------------------------
GitHub user ewencp opened a pull request:
https://github.com/apache/kafka/pull/486
KAFKA-2798: Use prefixedd configurations for Kafka Connect producer and consumer settings so they do not conflict with the distributed herder's settings.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ewencp/kafka kafka-2798-conflicting-herder-producer-consumer-configs
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/486.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 #486
----
commit d455acd938eb3e16d034ce0c4ac7899e541bc908
Author: Ewen Cheslack-Postava <me...@ewencp.org>
Date: 2015-11-10T18:52:56Z
KAFKA-2798: Use prefixedd configurations for Kafka Connect producer and consumer settings so they do not conflict with the distributed herder's settings.
----
> Kafka Connect distributed configs can conflict with producer/consumer configs, making it impossible to control them independently
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-2798
> URL: https://issues.apache.org/jira/browse/KAFKA-2798
> Project: Kafka
> Issue Type: Bug
> Components: copycat
> Reporter: Ewen Cheslack-Postava
> Assignee: Ewen Cheslack-Postava
>
> Right now we're using the approach to configs used by serializers where we just forward the configs for the entire worker to the producer and consumer. However, with the distributed mode, we now have a lot of conflicting configs because the distributed herder uses the group membership functionality and client networking libraries.
> We should instead use a sort of "namespaced" set of configs, which we already started doing with converters since we have multiple instances of converters instantiated by a single worker. We can use producer. and consumer. prefixes to isolate settings for the different components.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)