Hi dear Kafka team, I see that no matter what properties I give to the connector, the offset reset config for internal topics, especially the offset storage topic, say my-connect-offsets always use "earliest" which leads to very long bootstrap time during restart or stuck workers
Log sample and config sample print in the log 2025-08-12 10:10:45,531 INFO [Consumer clientId=cbdhk04-data-cluster-offsets, groupId=cbdhk04-data-cluster] Seeking to earliest offset of partition root@cbd:/usr/local/nxg/docker/kafka-connect# docker logs connect-replication-8085 | grep "auto.offset.reset = earliest" -C2 auto.commit.interval.ms = 5000 auto.include.jmx.reporter = true auto.offset.reset = earliest My connect-districuted.properties contains the following config producer.override.auto.offset.reset=latest consumer.override.auto.offset.reset=latest producer.auto.offset.reset=latest consumer.auto.offset.reset=latest auto.offset.reset=latest connector.client.config.override.policy=All None of the above can change the behaviour of the consumer initialized by connect to consume internal topics. What's the expected behaviour? How to improve the bootstrap time for havey connect cluster? What properties should I use to change the consumer config if possible at all. Thanks in advance -- *Imcom Jin* Software Engineer Manager, SEG T : +8613552756336 *NEXUSGUARD* www.nexusguard.com LinkedIn <https://www.linkedin.com/company/nexusguard> • Twitter <https://www.twitter.com/nexusguard> • Facebook <https://www.facebook.com/nxg.pr> Disclaimer: This e-mail message contains information intended solely for the intended recipient and is confidential or private in nature. If you are not the intended recipient, you must not read, disseminate, distribute, copy or otherwise use this message or any file attached to this message. Any such unauthorized use is prohibited and may be unlawful. If you have received this message in error, please notify the sender immediately by email, facsimile or telephone and then delete the original message from your machine.
