Optimize write throughput for Amazon Kinesis Data Streams
Big Data Blog
This article provides guidance on optimizing write throughput for Amazon Kinesis Data Streams and addressing write throughput exceeded errors.
Specifically, the article covers:
- Reasons for write throughput exceeded errors: exceeding overall stream throughput, hot shard issue, or hot key issue
- Identifying the cause using CloudWatch metrics, enhanced shard metrics, and the Kinesis Hot Shard Advisor (KHS) tool
- Remediation steps: adding shards, splitting hot shards, changing partition key scheme, or switching to on-demand capacity mode
- Overview of KHS tool for analyzing shard utilization and partition key distribution
- Conclusion on making Kinesis Data Streams applications more robust
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
May 3
2024
2024
Tune replication performance with AWS DMS for an Amazon Kinesis Data Streams target endpoint – Part 1
May 3
2024
2024
Tune replication performance with AWS DMS for an Amazon Kinesis Data Streams target endpoint – Part 2
Nov 20
2024
2024
Amazon Kinesis Data Streams On-Demand mode supports streams writing up to 10GB/s
Jan 17
2023
2023
Build highly available streams with Amazon Kinesis Data Streams
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.