[
https://issues.apache.org/jira/browse/KAFKA-9228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886767#comment-17886767
]
Doug Whitfield commented on KAFKA-9228:
---------------------------------------
{color:#172b4d}Members of my team believe the issue is that the connector is
not getting restarted. The log *says* it is creating a new connector. But the
connector has the same name. Should it be getting a new name?{color}
{color:#cccccc}[{color}{color:#6a9955}2024-10-02{color}{color:#cccccc}
{color}{color:#6a9955}14:40:32,162{color}{color:#cccccc}]
{color}{color:#b5cea8}INFO{color}{color:#cccccc} Scheduling a restart of
connector ec002i000948-kf002i000165-AP24944-mongosink-case in
{color}{color:#569cd6}600000{color}{color:#cccccc} ms
({color}{color:#569cd6}org.apache.kafka.connect.runtime.WorkerConfigTransformer{color}{color:#cccccc}:{color}{color:#569cd6}87{color}{color:#cccccc}){color}
{color:#cccccc}[{color}{color:#6a9955}2024-10-02{color}{color:#cccccc}
{color}{color:#6a9955}14:40:32,170{color}{color:#cccccc}]
{color}{color:#b5cea8}INFO{color}{color:#cccccc} Creating connector
ec002i000948-kf002i000165-AP24944-mongosink-case of type
{color}{color:#569cd6}com.mongodb.kafka.connect.MongoSinkConnector{color}{color:#cccccc}
({color}{color:#569cd6}org.apache.kafka.connect.runtime.Worker{color}{color:#cccccc}:{color}{color:#569cd6}309{color}{color:#cccccc}){color}
> 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: connect
> Affects Versions: 2.3.0, 2.4.0, 2.3.1, 2.3.2
> Reporter: Chris Egerton
> Assignee: Chris Egerton
> Priority: Major
> Fix For: 3.8.0, 3.7.1
>
>
> 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.20.10#820010)
