[
https://issues.apache.org/jira/browse/BEAM-6183?focusedWorklogId=173137&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-173137
]
ASF GitHub Bot logged work on BEAM-6183:
----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Dec/18 01:47
Start Date: 08/Dec/18 01:47
Worklog Time Spent: 10m
Work Description: chamikaramj commented on issue #7212: [BEAM-6183]
BigQuery insertAll API request rate is not properly controlled
URL: https://github.com/apache/beam/pull/7212#issuecomment-445419760
Can we implement shared backoff across threads as a solution to
https://issues.apache.org/jira/browse/BEAM-6183 before this ?
I think that should fix the bulk of the problem (sending too many requests
to BQ when quota errors are hit).
Looks like you are trying to implement client-side throttling for BQ in this
PR which could result in unintended performance issues in some cases.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 173137)
Time Spent: 20m (was: 10m)
> BigQuery insertAll API request rate is not properly controlled
> --------------------------------------------------------------
>
> Key: BEAM-6183
> URL: https://issues.apache.org/jira/browse/BEAM-6183
> Project: Beam
> Issue Type: Improvement
> Components: io-java-gcp
> Affects Versions: 2.8.0
> Reporter: Heejong Lee
> Assignee: Heejong Lee
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> BigQuery insertAll API request rate is not properly controlled so it produces
> too many rate limit exceeded error messages in the worker log.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
