[
https://issues.apache.org/jira/browse/BEAM-6443?focusedWorklogId=189221&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-189221
]
ASF GitHub Bot logged work on BEAM-6443:
----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jan/19 23:16
Start Date: 23/Jan/19 23:16
Worklog Time Spent: 10m
Work Description: reuvenlax commented on issue #7547: [BEAM-6443]
decrease the number of thread for BigQuery streaming inse…
URL: https://github.com/apache/beam/pull/7547#issuecomment-457004053
Ah yes - I thought the executor was being assigned in the constructor.
Ok, in that case I'm not sure what this PR is accomplishing. Essentially
every call to insertAll will create a new single-threaded executor. This is
no better than before. In fact I think it's worse - the unbounded executor
will reuse threads, while this PR will cause one to always be created. It's
not even per bundle, as insertAll can be called multiple times per bundle.
On Wed, Jan 23, 2019 at 3:05 PM Chamikara Jayalath <[email protected]>
wrote:
> Reuven, IIUC the proposal is to reduce parallelism to 50 threads per
> bundle (not a single thread per bundle).
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/beam/pull/7547#issuecomment-457001386>, or mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AUGE1XLNSUwsGiexUqHVjEcs4SB1p5SJks5vGOq0gaJpZM4aEV9P>
> .
>
----------------------------------------------------------------
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: 189221)
Time Spent: 1h 40m (was: 1.5h)
> 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: 1h 40m
> 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)
