Problem with the committed offsets while using KafkaSource and having the checkpointing enabled

Hi team! We have observed strange behavior when using KafkaSource and have checkpointing enabled. Even if we do not get checkpoint failures or any means of errors, we see the committed offset going up and down in a crazy manner instead of moving up to reach the end offset of that X topic. We know

Re: java.lang.UnsupportedOperationException: A serializer has already been registered for the state; re-registration is not allowed.

I would like again to thank you as we managed to fix this strange issue we had by moving all the state initializations into the open method of ProcessFunction! On Thu, Jan 18, 2024 at 11:53 PM Konstantinos Karavitis < kkaravi...@gmail.com> wrote: > Thank you very much Zakelly for taking

Re: java.lang.UnsupportedOperationException: A serializer has already been registered for the state; re-registration is not allowed.

ing a state in >> #processElement? >> >> >> Best, >> Zakelly >> >> On Thu, Jan 18, 2024 at 3:47 AM Konstantinos Karavitis < >> kkaravi...@gmail.com> wrote: >> >>> Have you ever met the following error when a flink application restarts &

java.lang.UnsupportedOperationException: A serializer has already been registered for the state; re-registration is not allowed.

Have you ever met the following error when a flink application restarts and tries to restore the state from RocksDB? *Caused by: java.lang.UnsupportedOperationException: A serializer has already been registered for the state; re-registration is not allowed. at org.apache.flink.runtime.state.State