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

Reply via email to