PLCyr commented on issue #1128:
URL:
https://github.com/apache/camel-kafka-connector/issues/1128#issuecomment-812127643
I did a test with camel-kafka-connector 0.7.3 and the behavior is good. The
idempotent topic is re-read from offset 0 after a connector crash (pod crash)
or connector configuration change. These lines in the log show the difference
[2021-04-01 19:20:00,722] INFO [Consumer
clientId=consumer-473c5e5a-e3e9-438e-8f92-8ae811cd2214-5,
groupId=473c5e5a-e3e9-438e-8f92-8ae811cd2214] **Seeking to EARLIEST offset** of
partition SFTP-Persistance-Topic-0
(org.apache.kafka.clients.consumer.internals.SubscriptionState)
[2021-04-01 19:20:00,729] INFO [Consumer
clientId=consumer-473c5e5a-e3e9-438e-8f92-8ae811cd2214-5,
groupId=473c5e5a-e3e9-438e-8f92-8ae811cd2214] Resetting offset for partition
SFTP-Persistance-Topic-0 to position FetchPosition{**offset=0**,
offsetEpoch=Optional.empty,
currentLeader=LeaderAndEpoch{leader=Optional[confluent-kafka-cp-kafka-2.confluent-kafka-cp-kafka-headless.kafka:9092
(id: 2 rack: null)], epoch=0}}.
(org.apache.kafka.clients.consumer.internals.SubscriptionState)
[2021-04-01 19:20:00,836] INFO Cache OK
(org.apache.camel.processor.idempotent.kafka.KafkaIdempotentRepository)
It's a good thing this fix will be include in the incoming
camel-kafka-connector 0.9.0 !
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
