GitHub user tzulitai opened a pull request:
https://github.com/apache/flink/pull/2432
[FLINK-4514][kinesis-connector] Handle unexpected ExpiredIteratorExceptions
Handle any unexpected {{ExpiredIteratorException}}s on {{getRecords()}}
calls be refreshing the failing shard iterator with a new one.
A user reported this issue when replaying Kinesis data over a wide time
span, but then the consumer was back to normal after the consumer caught up
with the latest data. I tried to reproduce the exception, but have come short
to be able to reproduce. The behaviour seems to be inconsistent.
Therefore, this change treats the exception as "unexpected" by simply
catching the exception and refreshing the iterator. There's actually no
guarantee of how much time had passed between each getRecords() request
anyways, so this is a simple way to handle this.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tzulitai/flink FLINK-4514
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2432.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2432
----
commit df833ddbca9971b5f03417efb65527408a8ad9c4
Author: Tzu-Li (Gordon) Tai <tzuli...@apache.org>
Date: 2016-08-29T09:30:39Z
[FLINK-4514][kinesis-connector] Handle unexpected ExpiredIteratorExceptions
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
