fix(inputs.kinesis_consumer): Ignore expired parent shards #17877
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.
Summary
When consuming Kinesis shards the code tries to begin as early as possible which, when resharding occured, means to start at the parent shards. However, in some cases the parent shards are already expired and therefore not accessible anymore (see documentation).
In the current code, this case is not handled and we rely on the parent shard being among the listed available shards. This assumption does not hold true for expired parent shards and thus the complete shard subgraph is not consumed.
This PR checks for expired parent shards and start consuming the present child shard in those cases.
Checklist
Related issues
resolves #17871