fix(esm/kinesis): Always store NextShardIterator from GetRecords #12677
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Currently, if an ESMs
MaximumBatchingWindowInSeconds
is0
AND no records are collected, a shard iterator never moves forward. This PR ensures that we will always update a shard's iterator value given a successfulGetRecords
call.Note, that any failures during processing should be handled by the internal retrier loop resulting in retrying the batch until successful or being discarded/sent to a DLQ. We should not be relying on the shard iterator value in order to keep track since these values are ephemeral and prone to expiry (i.e if a lambda processes for longer than 300s).
Changes
GetRecords
call.