Development Troubleshooting - Amazon Kinesis Data Analytics

Development Troubleshooting

Enabling Flamegraps

Due to its experimental nature in Flink, Flamegraphs are currently disabled by default as it may affect application performance. If you want to enable Flamegraphs for your application, create a case to request it to be enabled for you application ARN. For more information, see the AWS Support Center.

Issue with EFO connector 1.13.2

There is a known issue with the 1.13.2 Kinesis Data Streams EFO connector showing performance degradation if the application suffers from high backpressure. To mitigate, use the Flink 1.13.3 connector. You can use the 1.13-SNAPSHOT on Maven.

Compile Error: "Could not resolve dependencies for project"

In order to compile the Kinesis Data Analytics for Apache Flink sample applications, you must first download and compile the Apache Flink Kinesis connector and add it to your local Maven repository. If the connector hasn't been added to your repository, a compile error similar to the following appears:

Could not resolve dependencies for project your project name: Failure to find org.apache.flink:flink-connector-kinesis_2.11:jar:1.8.2 in was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced

To resolve this error, you must download the Apache Flink source code (version 1.8.2 from for the connector. For instructions about how to download, compile, and install the Apache Flink source code, see Using the Apache Flink Kinesis Streams Connector with previous Apache Flink versions.

Invalid Choice: "kinesisanalyticsv2"

To use v2 of the Kinesis Data Analytics API, you need the latest version of the AWS Command Line Interface (AWS CLI).

For information about upgrading the AWS CLI, see Installing the AWS Command Line Interface in the AWS Command Line Interface User Guide.

UpdateApplication Action Isn't Reloading Application Code

The UpdateApplication action will not reload application code with the same file name if no S3 object version is specified. To reload application code with the same file name, enable versioning on your S3 bucket, and specify the new object version using the ObjectVersionUpdate parameter. For more information about enabling object versioning in an S3 bucket, see Enabling or Disabling Versioning.