Hi Sankar,
First, as Alexey pointed out, please try and migrate to the Beam AWS SDK v2 as
soon as possible. The SDK v1 (including the Kinesis module) has been long
deprecated and will be removed some time soon.
The AWS API doesn’t support cross-account access for Kinesis using an ARN. This
is
hey we have a big job that fails after it hits BigQuery Storage API Read
quota limits, we’ve increased it once already but it keeps happening.
When a job fails we see a spike of 429 s on the API Monitoring page for
“ReadRows” and eventually we see "The worker lost contact with the service
in Datafl
Thanks Alexey and Moritz for your valuable inputs.
We were using ‘STSAssumeRoleSessionCredentialsProvider’ because of AWS SDKv1.
Now as per response and the issue, we will upgrade AWS SDK and Beam SDK and
give it a go. Will keep you posted on this in few days time. Thanks.
Regards,
Sankar
From
Damon (damondouglas) is working on a global throttling solution for Beam.
There should be a design doc shared here in a week or two.
However, you're right that the PR referenced should have addressed this. It
may be due for an update. Do you have time to take a look at the code and
see if it needs
Hi Kerry,
Thanks for the follow up, Michel Davit from the SCIO Slack workspace was
helpful in pointing out that this PR was actually not included in the code
I was running since it's only available in v2.43.0-RC2 right now.
I might try to run the release candidate if I get to it, but my code run