Hi Nik, Could you check outt the taskmanagers’ logs? When restored from a savepoint/checkpoint, FlinkKafkaConsumer would log the starting offset of Kafka partitions.
WRT `auto.offset.rest` in Kafka configuration, it’s of a relatively low priority, and would only be used when there’s no restored state plus FlinkKafkaConsumer is set to `startFromGroupOffset`. Best, Paul Lam > 在 2019年5月24日，07:50，Nikolas Davis <nda...@newrelic.com> 写道： > > Howdy, > > We're in the process of upgrading to 1.8. When restoring state to the new > cluster (using a savepoint) we are seeing our Kafka consumers restart from > the earliest offset. We're not receiving any other indication that our state > was not accepted as part of the deploy, e.g. we are not allowing unrestored > state, not receiving any errors. > > We have our consumers setup with the same consumer group and using the same > consumer (FlinkKafkaConsumer010) as our 1.4 deploy. > > Has anyone encountered this? Any idea what we might be doing wrong? > > What's also strange is that we are not setting auto.offset.reset, which > defaults to is largest (analogous to latest, correct?) -- which is not what > we're seeing happen. > > Regards, > > Nik
