Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.21.3, 4.3.0
-
None
-
Unknown
Description
Quoting https://github.com/abendton the pull request #12462:
- the shardId is not available in the exchange. The shardId is required to properly configure the GetShardIteratorRequest in the resume scenario (AWS doc)
- the KinesisResumeAdapter API does not allow to pass in the shardId.
- When consuming multiple shards the KinesisResumeAdapter will potentially be used by multiple threads concurrently. With the current API, this could cause concurrency issues
Attachments
Issue Links
- links to