Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
2.17.0
-
None
-
None
-
Unknown
Description
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