Project using version 2.4.3 of KCL that has a defect

[chrishirestreet]

We received the following notification from AWS that our snowplow enrich server is using a defective version of the Kinesis Client Library (KCL).

Any chance that there could be a version upgrade for KCL in this project, even just to 2.6.1?

You are receiving this notification as we have identified that your account uses Amazon Kinesis Data Streams with clients using Kinesis Client Library (KCL) [1] 2.x versions prior to 2.6.1. We have discovered a defect in KCL 2.x versions prior to 2.6.1 that may block shard processing after a data stream has scaled up or scaled down. We strongly recommend upgrading your KCL applications to version 2.6.1 or later. The issue is fully resolved in the KCL version 2.6.1 [2] or later.

A list of the KCL versions you are using that should be upgraded to KCL 2.6.1 or later can be found in the "Affected resources" tab.

You can find the latest KCL version in the KCL GitHub repository [3]. KCL version 1.x and 3.x are not impacted.

For any additional questions or concerns, please reach out to AWS Support [4].

[1] https://docs.aws.amazon.com/streams/latest/dev/kcl.html
[2] https://github.com/awslabs/amazon-kinesis-client/releases/tag/v2.6.1
[3] https://github.com/awslabs/amazon-kinesis-client
[4] https://aws.amazon.com/support

[stanch]

Hi @chrishirestreet, thanks for letting us know!

We’ve indeed observed this behavior over the years. Note that it’s infrequent across the hundreds of services we manage that consume from Kinesis. That said, we have typically resolved the issue with a manual or an automatic (via EKS and health probes) restart. So it’s great that a fix is now available for 2.x, which should be a simpler upgrade.

We’ll add that to the backlog for Enrich and other relevant services.