[ 
https://issues.apache.org/jira/browse/KAFKA-9228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886421#comment-17886421
 ] 

Doug Whitfield commented on KAFKA-9228:
---------------------------------------

[~gharris1727] thanks!

I will have to try to get more logs from the team with access, but in what I 
currently have, I do not see either of those errors.

The thing that I see is this weird (to me) double restart:
{color:#cccccc}[{color}{color:#6a9955}2024-09-11{color}{color:#cccccc} 
{color}{color:#6a9955}20:16:55,988{color}{color:#cccccc}] 
{color}{color:#b5cea8}INFO{color}{color:#cccccc} Scheduling a restart of 
connector 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-09-11{color}{color:#cccccc} 
{color}{color:#6a9955}20:16:55,989{color}{color:#cccccc}] 
{color}{color:#b5cea8}INFO{color}{color:#cccccc} Retrieving config data from 
path 
{color}{color:#ce9178}'/apps/kafka/creds/creds.properties'{color}{color:#cccccc}
 
({color}{color:#569cd6}com.lonecppcoder.kafka.config.TTLFileConfigProvider{color}{color:#cccccc}:{color}{color:#569cd6}91{color}{color:#cccccc}){color}
{color:#cccccc}[{color}{color:#6a9955}2024-09-11{color}{color:#cccccc} 
{color}{color:#6a9955}20:16:56,143{color}{color:#cccccc}] 
{color}{color:#b5cea8}INFO{color}{color:#cccccc} the value of the key = 
{color}{color:#ce9178}'password'{color}{color:#cccccc} is 
{color}{color:#ce9178}''{color}{color:#cccccc} 
({color}{color:#569cd6}com.lonecppcoder.kafka.config.TTLFileConfigProvider{color}{color:#cccccc}:{color}{color:#569cd6}102{color}{color:#cccccc}){color}
{color:#cccccc}[{color}{color:#6a9955}2024-09-11{color}{color:#cccccc} 
{color}{color:#6a9955}20:16:56,143{color}{color:#cccccc}] 
{color}{color:#b5cea8}INFO{color}{color:#cccccc} the value of the key = 
{color}{color:#ce9178}'username'{color}{color:#cccccc} is 
{color}{color:#ce9178}'NGUouaMNpuRd6XCF2wyr-1726085638'{color}{color:#cccccc} 
({color}{color:#569cd6}com.lonecppcoder.kafka.config.TTLFileConfigProvider{color}{color:#cccccc}:{color}{color:#569cd6}102{color}{color:#cccccc}){color}
{color:#cccccc}[{color}{color:#6a9955}2024-09-11{color}{color:#cccccc} 
{color}{color:#6a9955}20:16:56,143{color}{color:#cccccc}] 
{color}{color:#b5cea8}INFO{color}{color:#cccccc} Returning new config data with 
TTL {color}{color:#ce9178}'600000'{color}{color:#cccccc} 
({color}{color:#569cd6}com.lonecppcoder.kafka.config.TTLFileConfigProvider{color}{color:#cccccc}:{color}{color:#569cd6}106{color}{color:#cccccc}){color}
{color:#cccccc}[{color}{color:#6a9955}2024-09-11{color}{color:#cccccc} 
{color}{color:#6a9955}20:16:56,144{color}{color:#cccccc}] 
{color}{color:#b5cea8}INFO{color}{color:#cccccc} Scheduling a restart of 
connector 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-09-11{color}{color:#cccccc} 
{color}{color:#6a9955}20:16:56,144{color}{color:#cccccc}] 
{color}{color:#b5cea8}INFO{color}{color:#cccccc} Retrieving config data from 
path 
{color}{color:#ce9178}'/apps/kafka/creds/creds.properties'{color}{color:#cccccc}
 
({color}{color:#569cd6}com.lonecppcoder.kafka.config.TTLFileConfigProvider{color}{color:#cccccc}:{color}{color:#569cd6}91{color}{color:#cccccc}){color}
{color:#cccccc}[{color}{color:#6a9955}2024-09-11{color}{color:#cccccc} 
{color}{color:#6a9955}20:16:56,176{color}{color:#cccccc}] 
{color}{color:#b5cea8}INFO{color}{color:#cccccc} the value of the key = 
{color}{color:#ce9178}'password'{color}{color:#cccccc} is 
{color}{color:#ce9178}''{color}{color:#cccccc} 
({color}{color:#569cd6}com.lonecppcoder.kafka.config.TTLFileConfigProvider{color}{color:#cccccc}:{color}{color:#569cd6}102{color}{color:#cccccc}){color}
{color:#cccccc}[{color}{color:#6a9955}2024-09-11{color}{color:#cccccc} 
{color}{color:#6a9955}20:16:56,176{color}{color:#cccccc}] 
{color}{color:#b5cea8}INFO{color}{color:#cccccc} the value of the key = 
{color}{color:#ce9178}'username'{color}{color:#cccccc} is 
{color}{color:#ce9178}'NGUouaMNpuRd6XCF2wyr-1726085638'{color}{color:#cccccc} 
({color}{color:#569cd6}com.lonecppcoder.kafka.config.TTLFileConfigProvider{color}{color:#cccccc}:{color}{color:#569cd6}102{color}{color:#cccccc}){color}
{color:#cccccc}[{color}{color:#6a9955}2024-09-11{color}{color:#cccccc} 
{color}{color:#6a9955}20:16:56,177{color}{color:#cccccc}] 
{color}{color:#b5cea8}INFO{color}{color:#cccccc} Returning new config data with 
TTL {color}{color:#ce9178}'600000'{color}{color:#cccccc} 
({color}{color:#569cd6}com.lonecppcoder.kafka.config.TTLFileConfigProvider{color}{color:#cccccc}:{color}{color:#569cd6}106{color}{color:#cccccc}){color}
 
{color:#172b4d}The fact that it retries is of course not weird in and of 
itself, but there is no timeout error or anything to suggest why it happens 
twice.{color}
 
{color:#172b4d}{color:#172b4d}On a later day with a higher logging level there 
are a couple of these that are blank
{color}{color}
{color:#cccccc}[{color}{color:#6a9955}2024-09-19{color}{color:#cccccc} 
{color}{color:#6a9955}09:14:36,905{color}{color:#cccccc}] 
{color}{color:#569cd6}DEBUG{color}{color:#cccccc} [Worker 
clientId={color}{color:#569cd6}connect-198.18.155.99{color}{color:#cccccc}:{color}{color:#569cd6}8089{color}{color:#cccccc},
 groupId=streamconnect-case] Tasks to restart from currently running 
assignment: [] 
({color}{color:#569cd6}org.apache.kafka.connect.runtime.distributed.DistributedHerder{color}{color:#cccccc}:{color}{color:#569cd6}1933{color}{color:#cccccc})
{color}
 
{color:#172b4d}Then there is one where it does get scheduled{color}
{color:#cccccc}[{color}{color:#6a9955}2024-09-19{color}{color:#cccccc} 
{color}{color:#6a9955}09:14:38,187{color}{color:#cccccc}] 
{color}{color:#569cd6}DEBUG{color}{color:#cccccc} [Worker 
clientId={color}{color:#569cd6}connect-198.18.155.99{color}{color:#cccccc}:{color}{color:#569cd6}8089{color}{color:#cccccc},
 groupId=streamconnect-case] Tasks to restart from currently running 
assignment: [mongosink-case-{color}{color:#569cd6}1{color}{color:#cccccc}, 
mongosink-case-{color}{color:#569cd6}0{color}{color:#cccccc}] 
({color}{color:#569cd6}org.apache.kafka.connect.runtime.distributed.DistributedHerder{color}{color:#cccccc}:{color}{color:#569cd6}1933{color}{color:#cccccc}){color}
 
{color:#172b4d}This is all running in Kubernetes so it's possible the reason I 
am not seeing those errors is because the pod is automatically getting 
restarted before that happens. I will have to discuss with the team "on the 
ground" to see if they are happy accepting 17627, but will ask them to not 
restart the pods to see if we can perhaps see some different errors.{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)

Reply via email to