beam-commits mailing list archives

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


Solomon Duskis commented on BEAM-1269:

BigtableIO should not set data channel pool counts for reads.  This is the current line:

      // Set data channel count to one because there is only 1 scanner in this session
      BigtableOptions.Builder clonedBuilder = options.toBuilder()
      BigtableOptions optionsWithAgent =

It should be more like:

     BigtableOptions optionsWithAgent = options
             . setUseCachedDataPool(true)
             . setDataHost(BigtableOptions.BIGTABLE_BATCH_DATA_HOST_DEFAULT)

> BigtableIO should make more efficient use of connections
> --------------------------------------------------------
>                 Key: BEAM-1269
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-gcp
>            Reporter: Daniel Halperin
>              Labels: newbie, starter
> 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

This message was sent by Atlassian JIRA

View raw message