You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are experiencing very frequent LimitExceededExceptions when starting our kinsumer applications. This is a result of the hard 10 TPS rate limit on DescribeStream calls in AWS.
Right now we are avoiding this by creating a kinsumer with the NewWithInterfaces constructor and passing in a custom kinesisiface.KinesisAPI with a workaround implementation of DescribeStream that calls ListShards instead.
It would be great if there was a config toggle to use an alternate method to check kenesis stream readiness so that we can avoid this issue.
The text was updated successfully, but these errors were encountered:
Hi, @StevenMcVicker I'll take a look soon, but are you using the latest? I thought that #21 addressed this (if it doesn't I'm just going by the description of the issue and it might not be related)
We are experiencing very frequent LimitExceededExceptions when starting our kinsumer applications. This is a result of the hard 10 TPS rate limit on DescribeStream calls in AWS.
Right now we are avoiding this by creating a kinsumer with the NewWithInterfaces constructor and passing in a custom kinesisiface.KinesisAPI with a workaround implementation of DescribeStream that calls ListShards instead.
It would be great if there was a config toggle to use an alternate method to check kenesis stream readiness so that we can avoid this issue.
The text was updated successfully, but these errors were encountered: