Skip to content

Conversation

@srebhan
Copy link
Member

@srebhan srebhan commented Oct 23, 2025

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

  • No AI generated code was used in this PR

Related issues

resolves #17871

@telegraf-tiger telegraf-tiger bot added fix pr to fix corresponding bug plugin/input 1. Request for new input plugins 2. Issues/PRs that are related to input plugins labels Oct 23, 2025
@telegraf-tiger
Copy link
Contributor

@srebhan srebhan added the area/aws AWS plugins including cloudwatch, ecs, kinesis label Oct 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/aws AWS plugins including cloudwatch, ecs, kinesis fix pr to fix corresponding bug plugin/input 1. Request for new input plugins 2. Issues/PRs that are related to input plugins

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[[inputs.kinesis_consumer]] Kinesis Consumer does not consume messages since v1.34.0

3 participants