beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Solomon Duskis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-1269) BigtableIO should make more efficient use of connections
Date Wed, 29 Mar 2017 18:23:41 GMT

    [ https://issues.apache.org/jira/browse/BEAM-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947642#comment-15947642
] 

Solomon Duskis commented on BEAM-1269:
--------------------------------------

Cloud Bigtable client 0.9.6 was just released, and should be flowing through the maven repo
process now.

This feature can be invoked via BigtableOptions.setUseCachedDataPool(true)

I have a follow up request to also set BigtableOptions.setDataHost(BigtableOptions.BIGTABLE_BATCH_DATA_HOST_DEFAULT)
which will be a host dedicated to Batch type workloads like Dataflow.

> BigtableIO should make more efficient use of connections
> --------------------------------------------------------
>
>                 Key: BEAM-1269
>                 URL: https://issues.apache.org/jira/browse/BEAM-1269
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-gcp
>            Reporter: Daniel Halperin
>
> RIght now, {{BigtableIO}} opens up a new Bigtable session for every DoFn, in the {{@Setup}}
function. However, sessions can support multiple connections, so perhaps this code should
be modified to open up a smaller session pool and then allocation connections in {{@StartBundle}}.
> This would likely make more efficient use of resources, especially for highly multithreaded
workers.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message