You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/01/17 19:01:00 UTC
[jira] [Work logged] (BEAM-6443) decrease the number of threads for
BigQuery streaming insertAll
[ https://issues.apache.org/jira/browse/BEAM-6443?focusedWorklogId=186493&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-186493 ]
ASF GitHub Bot logged work on BEAM-6443:
----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Jan/19 19:00
Start Date: 17/Jan/19 19:00
Worklog Time Spent: 10m
Work Description: ihji commented on issue #7547: [BEAM-6443] decrease the number of thread for BigQuery streaming inse…
URL: https://github.com/apache/beam/pull/7547#issuecomment-455289951
R: @chamikaramj, @udim
----------------------------------------------------------------
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:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 186493)
Time Spent: 20m (was: 10m)
> decrease the number of threads for BigQuery streaming insertAll
> ---------------------------------------------------------------
>
> Key: BEAM-6443
> URL: https://issues.apache.org/jira/browse/BEAM-6443
> Project: Beam
> Issue Type: Improvement
> Components: io-java-gcp
> Reporter: Heejong Lee
> Assignee: Heejong Lee
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When inserting (a large number of ) very small elements into BigQuery via streaming insertAll, BigQueryIO causes lots of quota exceeded errors. This implies that 1) BigQueryIO puts unnecessary overheads on BigQuery API layer by sending requests too fast 2) log file becomes very big because of repeated same error messages. Currently we use 50 shards for writing data into BigQuery and in each bundle 20-30 futures are executed simultaneously with unlimited thread pool. It would be worth investigating whether just single thread pool is sufficient for running concurrent insertAll.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)