Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-9228

Reconfigured converters and clients may not be propagated to connector tasks

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.3.0, 2.4.0, 2.3.1, 2.3.2
    • Fix Version/s: None
    • Component/s: KafkaConnect
    • Labels:
      None

      Description

      If an existing connector is reconfigured but the only changes are to its converters and/or Kafka clients (enabled as of KIP-458), 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, and neither of those contain converter or Kafka client configs.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ChrisEgerton Chris Egerton
                Reporter:
                ChrisEgerton Chris Egerton
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: