Hi Josh,
Thanks for the description. From your description and a check into the code,
I’m suspecting what could be happening is that before the consumer caught up to
the head of the stream, Kinesis was somehow returning the same shard iterator
on consecutive fetch calls, and the consumer kept o
Hi Gordon,
My job only went down for around 2-3 hours, and I'm using the default
Kinesis retention of 24 hours. When I restored the job, it got this
exception after around 15 minutes (and then restarted again, and got the
same exception 15 minutes later etc) - but actually I found that after this
Hi Josh,
Thank you for reporting this, I’m looking into it. There was some major changes
to the Kinesis connector after mid June, but the changes don’t seem to be
related to the iterator timeout, so it may be a bug that had always been there.
I’m not sure yet if it may be related, but may I ask
Hi all,
I guess this is probably a question for Gordon - I've been using the
Flink-Kinesis connector for a while now and seen this exception a couple of
times:
com.amazonaws.services.kinesis.model.ExpiredIteratorException:
Iterator expired. The iterator was created at time Fri Aug 26 10:47:47
UTC
