Hi Jeremiah, >> why is the offset 0?
This likely means that the change-log is empty and does not have any messages. Can you try consuming from partition-number: 0 using a KafkaConsumer? Best, Jagadish On Fri, Mar 22, 2019 at 11:45 AM Jeremiah Adams <jad...@helixeducation.com> wrote: > I'm seeing these in our log periodically and havn't seen them before. > Does this imply that the topic associated with the change log is being > replayed from the beginning? > > > Also, why is the offset 0? It definitely should not be. We have messages > across all partitions. > > > 2019-03-22 18:30:24 KafkaSystemAdmin [INFO] Fetching SSP metadata for: > [SystemStreamPartition [kafka, delivery-changelog, 0]] > 2019-03-22 18:30:24 KafkaSystemAdmin [WARN] Empty Kafka topic partition > delivery-changelog-0 with upcoming offset 0. Skipping newest offset and > setting oldest offset to 0 to consume from beginning > 2019-03-22 18:30:52 KafkaSystemAdmin [INFO] Fetching SSP metadata for: > [SystemStreamPartition [kafka, delivery-changelog, 0]] > 2019-03-22 18:30:52 KafkaSystemAdmin [WARN] Empty Kafka topic partition > delivery-changelog-0 with upcoming offset 0. Skipping newest offset and > setting oldest offset to 0 to consume from beginning > > > Jeremiah Adams > Software Engineer > www.helixeducation.com<http://www.helixeducation.com/> > Blog<http://www.helixeducation.com/blog/> | Twitter< > https://twitter.com/HelixEducation> | Facebook< > https://www.facebook.com/HelixEducation> | LinkedIn< > http://www.linkedin.com/company/3609946> > -- Jagadish V, Graduate Student, Department of Computer Science, Stanford University
