2 個答案
- 最新
- 最多得票
- 最多評論
0
This is expected behavior. If you had more than one shard, you will notice that the KCL will load balance across those two instances. Kinesis shards are usually meant to be consumed in a serial fashion by a single thread per shard. This helps with maintaining ordering guarantees within a shard, and makes things like the checkpointing logic simple and co-ordination free.
已回答 4 年前
0
Thanks Rohit for confirming, this is the exact behavior observed by me. So once I have increased the shard size from 1 to 2, both of my instances that belong to same application starts receiving the messages from each shard. I still think documentation should be more clear for these real world edge cases.
已回答 4 年前
相關內容
- AWS 官方已更新 5 個月前
- AWS 官方已更新 5 個月前