[
https://issues.apache.org/jira/browse/BEAM-6443?focusedWorklogId=195386&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-195386
]
ASF GitHub Bot logged work on BEAM-6443:
----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Feb/19 22:14
Start Date: 06/Feb/19 22:14
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-461209437
run java postcommit
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 195386)
Time Spent: 2h (was: 1h 50m)
> 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: 2h
> 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)
