You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2016/01/21 10:14:39 UTC

[jira] [Updated] (CAMEL-9515) Does not handle an expired iterator exception

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

Claus Ibsen updated CAMEL-9515:
-------------------------------
    Assignee: Andrew Wheat

> Does not handle an expired iterator exception
> ---------------------------------------------
>
>                 Key: CAMEL-9515
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9515
>             Project: Camel
>          Issue Type: Improvement
>    Affects Versions: 2.17.0
>            Reporter: Andrew Wheat
>            Assignee: Andrew Wheat
>            Priority: Minor
>             Fix For: 2.17.0
>
>
> Given a running poll that has processed some records from the stream
> When the AWS DDB Stream is unavailable for greater than the shard iterator expiry time (currently 15 mins) and less than the trim horizon (currently 24 hours)
> And then becomes available again
> Then the consumer gets stuck trying to request data for a shard that has expired
> Expected Behaviour:
> Then the consumer should be able to resume from where it left off



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