Details
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
Attachments
Issue Links
- is related to
-
KAFKA-17704 possible race condition in TTL credentials when connectors recycled on single node instance
-
- Open
-
- relates to
-
KAFKA-16837 Kafka Connect fails on update connector for incorrect previous Config Provider tasks
-
- Resolved
-
-
KAFKA-17627 ConfigProvider TTLs do not restart Tasks
-
- Patch Available
-
- links to