[BEAM-13443] Poor handling of aggregated records in KinesisIO.read

• Type: Bug
• Status: Resolved
• Priority: P2
• Resolution: Fixed
• Fix Version/s: 2.36.0
• Component/s: io-java-aws
• Labels: aws aws-sdk-v1 aws-sdk-v2 performance
• Assignee: Moritz Mack
• Reporter: Moritz Mack
• Created: 13/Dec/21 08:04
• Updated: 20/Dec/21 17:12
• Resolved: 20/Dec/21 17:12

Description

The way the Kinesis source is implemented it doesn't play well with aggregated records.

Even using configuration options it's fairly hard to configure it in a way that becomes sufficiently performant.

One of the key issues is around bundle size & record queue size vs the number of aggregated records per message. These might, in certain situations, exceed the internal queue size by far unnecessarily blocking threads and requiring thread pools to be forcefully taken down.

 

Issue Links

• links to: GitHub Pull Request #16286