You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jamie Grier (JIRA)" <ji...@apache.org> on 2019/02/14 13:30:00 UTC
[jira] [Updated] (FLINK-11617) Kinesis Connector getRecords()
failure logging is misleading
[ https://issues.apache.org/jira/browse/FLINK-11617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie Grier updated FLINK-11617:
--------------------------------
Description: There isn't enough information in the current logging to diagnose a getRecords() failure. Also there is a hardcoded string that states the failure cause was always ProvisionedThroughputExceededException which isn't true. There are many possible causes of failures. This is misleading. (was: My Flink job that consumes from a Kinesis stream must be restarted at least once daily due to an uncaught AmazonKinesisException when reading from Kinesis. The complete stacktrace looks like:
{noformat}
com.amazonaws.services.kinesis.model.AmazonKinesisException: null (Service: AmazonKinesis; Status Code: 500; Error Code: InternalFailure; Request ID: dc1b7a1a-1b97-1a32-8cd5-79a896a55223)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1545)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1183)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:964)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:676)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:650)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:633)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$300(AmazonHttpClient.java:601)
at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:583)
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:447)
at com.amazonaws.services.kinesis.AmazonKinesisClient.doInvoke(AmazonKinesisClient.java:1747)
at com.amazonaws.services.kinesis.AmazonKinesisClient.invoke(AmazonKinesisClient.java:1723)
at com.amazonaws.services.kinesis.AmazonKinesisClient.getRecords(AmazonKinesisClient.java:858)
at org.apache.flink.streaming.connectors.kinesis.proxy.KinesisProxy.getRecords(KinesisProxy.java:193)
at org.apache.flink.streaming.connectors.kinesis.internals.ShardConsumer.getRecords(ShardConsumer.java:268)
at org.apache.flink.streaming.connectors.kinesis.internals.ShardConsumer.run(ShardConsumer.java:176)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{noformat}
It's interesting that the Kinesis endpoint returned a 500 status code, but that's outside the scope of this issue.
I think we can handle this exception in the same manner as a ProvisionedThroughputException: performing an exponential backoff and retrying a finite number of times before throwing an exception.)
> Kinesis Connector getRecords() failure logging is misleading
> ------------------------------------------------------------
>
> Key: FLINK-11617
> URL: https://issues.apache.org/jira/browse/FLINK-11617
> Project: Flink
> Issue Type: Improvement
> Components: Kinesis Connector
> Affects Versions: 1.5.6, 1.6.3, 1.7.1
> Reporter: Jamie Grier
> Assignee: Jamie Grier
> Priority: Major
>
> There isn't enough information in the current logging to diagnose a getRecords() failure. Also there is a hardcoded string that states the failure cause was always ProvisionedThroughputExceededException which isn't true. There are many possible causes of failures. This is misleading.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)