You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Chris Egerton (Jira)" <ji...@apache.org> on 2019/11/23 01:14:00 UTC

[jira] [Created] (KAFKA-9228) Reconfigured converters and clients may not be propagated to connector tasks

Chris Egerton created KAFKA-9228:
------------------------------------

             Summary: Reconfigured converters and clients may not be propagated to connector tasks
                 Key: KAFKA-9228
                 URL: https://issues.apache.org/jira/browse/KAFKA-9228
             Project: Kafka
          Issue Type: Bug
          Components: KafkaConnect
    Affects Versions: 2.3.0, 2.4.0, 2.3.1, 2.3.2
            Reporter: Chris Egerton
            Assignee: Chris Egerton


If an existing connector is reconfigured but the only changes are to its converters and/or Kafka clients (enabled as of [KIP-458|https://cwiki.apache.org/confluence/display/KAFKA/KIP-458%3A+Connector+Client+Config+Override+Policy]), the changes will not propagate to its tasks unless the connector also generates task configs that differ from the existing task configs. Even after this point, if the connector tasks are reconfigured, they will still not pick up on the new converter and/or Kafka client configs.

This is because the {{DistributedHerder}} only writes new task configurations to the connect config topic [if the connector-provided task configs differ from the task configs already in the config topic|https://github.com/apache/kafka/blob/e499c960e4f9cfc462f1a05a110d79ffa1c5b322/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/distributed/DistributedHerder.java#L1285-L1332], and neither of those contain converter or Kafka client configs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)