You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org> on 2016/10/05 03:58:21 UTC

[jira] [Updated] (FLINK-4514) ExpiredIteratorException in Kinesis Consumer on long catch-ups to head of stream

     [ https://issues.apache.org/jira/browse/FLINK-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tzu-Li (Gordon) Tai updated FLINK-4514:
---------------------------------------
    Fix Version/s:     (was: 1.1.2)
                   1.1.3

> ExpiredIteratorException in Kinesis Consumer on long catch-ups to head of stream
> --------------------------------------------------------------------------------
>
>                 Key: FLINK-4514
>                 URL: https://issues.apache.org/jira/browse/FLINK-4514
>             Project: Flink
>          Issue Type: Bug
>          Components: Kinesis Connector
>    Affects Versions: 1.1.0, 1.1.1
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Tzu-Li (Gordon) Tai
>             Fix For: 1.2.0, 1.1.3
>
>
> Original mailing thread for the reported issue:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Kinesis-connector-Iterator-expired-exception-td8711.html
> Normally, the exception is thrown when the consumer uses the same shard iterator after 5 minutes since it was retrieved. I've still yet to clarify & reproduce the root cause of the {{ExpiredIteratorException}}, because from the code this seems to be impossible. I'm leaning towards suspecting this is a Kinesis-side issue (from the description in the ML, the behaviour also seems indeterminate).
> Either way, the exception can be fairly easily handled so that the consumer doesn't just fail. When caught, we request a new shard iterator from Kinesis with the last sequence number.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)