ProvisionedThroughputExceededException in kinesis client library about amazon-kinesis-client

[pfifer]

Thanks for reporting this. We'll look at handling the throttling exception, and reporting it at a lower logging level.

[rantav]

Thank you @kumarumesh so in this case, I'd appreciate it if you could level down the log message to INFO or at least WARN. I regard ERROR as something that needs to be taken care of immediately, not benign,

[NathanChristie]

I also support lowering this to the warning level.

[arisha84]

Hi Rantav,

I got this error as well.
Notice that there is a limitation of 5 getRecord requests per second per shard and 1000 puts per second per shard.
You should take it into account when you determine the number of shards in your stream.

This is very important and can cause you a lot of problems!

for example if you read less than 1Mb/sec from each shard (the max is 2Mb/sec), but you do it in 7 getRecord requests/sec you will get ProvisionedThroughputExceededException and you'll probably don't know why. It may cause your applications to have delays on the stream

To solve this you need to do some fine tuning on your KinesisClientLibConfiguration - you can control the maxRecords in each read and the idleTimeBetweenReadsInMillis.
Lets say you have 7 applications working on a stream - if the idleTimeBetweenReadsInMillis is 1000 (1 sec) you'll probably get a lot of those exceptions. In this case you'll want to increase the idle time to 2 seconds. Also you want to read as many records as possible in each getRecords call, so I recommend setting maxRecords to 10000 (the max value allowed).

Hope this helps,
Ari.

[pfifer]

This has been fixed in the latest release. It will now be a warning unless it's throttled 6 times consecutively. Additionally the message is now reported from the the ThrottleReporter if you want to filter it out completely.

Feel free to reopen if you have any other questions or concerns.

[kirill-kozlov]

Hey, is it possible to migrate the implemented functionality to 2.X version also?
There is an open request about it: #539

[kumarumesh]

Hi Rantav,

Thanks for reporting this.

As you said, if you see this exception occasionally, and your application (that uses KCL to process Kinesis stream) doesn't fall behind in processing your Kinesis stream data, then it can be considered as a benign exception and can be ignored.

We recently updated our documentation to reflect this ( for details see section titled "Read Throttling" at http://docs.aws.amazon.com/kinesis/latest/dev/kinesis-record-processor-additional-considerations.html )

Let me know if you have further questions.

Thanks
Umesh

[f-ganz]

+1

[preetpuri]

I agree this should be lower down to warn level

[SmiddyPence]

+1 For a Warn

[zackhsi]

+1