Hi, we're investigating an issue where occasionally config changes don't propagate to connectors/tasks.
When this occurs, the only way to ensure that the configuration takes effect is to resize the number of tasks back down to 1 and then resize back up to the original number of tasks. In searching for others who have been bitten by this scenario we found the following thread on the Strimzi discussions pages: https://github.com/strimzi/strimzi-kafka-operator/discussions/7738 Both the symptoms and workaround described there match what we've seen.We've been doing some digging into the Kafka Connect codebase to better understand how config.storage.topic is consumed. In the interest of brevity I won't repeat that entire thread of discussion here. However, I was wondering if anyone knows whether the JavaDoc suggestion on ClusterConfigState.inconsistentConnectors() is actually implemented in the clustered Worker code.i.e. "When a worker detects a connector in this state, it should request that the connector regenerate its task configurations." The reason I ask is because I couldn't find any references to that API call anywhere but in the KafkaConfigBackingStoreTest unit test cases. Thanks!
