Stay up to date with the latest from the Knowledge Center. See all new and updated Knowledge Center articles published in the last month and re:Post’s top contributors.
Kinesis datastream iterator age is high
Hi,
We have a system where we ingest data via kinesis data stream, connected to kinesis firehose, and outputted to s3. Occasionally and seemingly arbitrarily, our monitor on GetRecords iterator age maximum > 5mins would trigger for a few hours at a time.
We added many more shards to the data stream than required (write throughput at <10% capacity), but had no impact.
According to the docs, When Kinesis Data Streams is configured as the data source, this quota doesn't apply, and Kinesis Data Firehose scales up and down with no limit. so it should not be a capacity issue here either.
What could cause this to happen?
- Newest
- Most votes
- Most comments
Hi,
Check this indicating reasons of having an increasing iterator age on the Kinesis Data Stream.
As hints, check if there are
- Any read throttles on the stream
- Even distribution of data on the shards
- Any other consumer on the stream other than the Firehose
Relevant content
- asked 2 years ago
- asked 10 months ago
- asked 3 years ago
AWS OFFICIALUpdated 3 years ago- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
