[
https://issues.apache.org/jira/browse/KAFKA-17704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887951#comment-17887951
]
Dmitri Pavlov commented on KAFKA-17704:
---------------------------------------
Updated the code like this > basically added extra logging.
if (!result) {
Map<String, String> appliedConnectorConfig =
configState.appliedConnectorConfig(connName);
Map<String, String> currentConnectorConfig =
configState.connectorConfig(connName);
// Log the values of appliedConnectorConfig and currentConnectorConfig
*log.debug("Applied Connector Config for {}: {}", connName,
appliedConnectorConfig);*
*log.debug("Current Connector Config for {}: {}", connName,
currentConnectorConfig);*
if (!Objects.equals(appliedConnectorConfig, currentConnectorConfig)) {
log.debug("Forcing task restart for connector {} as its configuration
appears to be updated", connName);
result = true;
}
}
Here is the output
!image-2024-10-09-17-04-31-915.png!
Between 13:53 and 15:55 I changed the creds from user4:password4 to
user1:password1 and it thinks the applied config (i.e. the previous value) is
user1. But it was user4. That is why thinks unchanged. Before 13:53 I updated
the user from user3:password3 to user4:password4 and the change was detected
correctly. Does not look correct.
> possible race condition in TTL credentials when connectors recycled on single
> node instance
> -------------------------------------------------------------------------------------------
>
> Key: KAFKA-17704
> URL: https://issues.apache.org/jira/browse/KAFKA-17704
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 3.7.1
> Reporter: Doug Whitfield
> Priority: Minor
> Attachments: For_community.zip.001, For_community.zip.002,
> For_community.zip.003, For_community.zip.004, For_community.zip.005,
> For_community.zip.006, For_community.zip.007,
> image-2024-10-07-11-17-41-951.png, image-2024-10-08-19-10-13-215.png,
> image-2024-10-09-17-04-31-915.png, logstoupload.log
>
>
> This is related to https://issues.apache.org/jira/browse/KAFKA-9228 and
> https://issues.apache.org/jira/browse/KAFKA-17627 but in single node instance
> and only related to credentials (as far as we know currently), so maybe
> something else is in play?
> In some cases, when TTL is used with a single node, passwords are not passed
> properly.
> In the "logstoupload.log" file you can see that at 09:14 the password does
> not get change, but at 09:24 it does get changed.
> We are able to "reliably" reproduce this in prod-like environment where this
> log comes from in Kubernetes, but we have only captured this "race condition"
> in test rarely where we are not using Kubernetes. We have seen it without
> Kubernetes though.
> We hope to provide something more reproducible next week, but perhaps
> uploading this "full" log will allow you to guide us so we can make this more
> reproducible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
