You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Joshua (JIRA)" <ji...@apache.org> on 2019/03/03 10:59:00 UTC
[jira] [Updated] (BEAM-6764) OutOfMemory Exception in Dataflow
Spanner Write Mutations
[ https://issues.apache.org/jira/browse/BEAM-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua updated BEAM-6764:
-------------------------
Component/s: (was: io-java-mqtt)
io-java-gcp
> OutOfMemory Exception in Dataflow Spanner Write Mutations
> ---------------------------------------------------------
>
> Key: BEAM-6764
> URL: https://issues.apache.org/jira/browse/BEAM-6764
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Affects Versions: 2.10.0, 2.11.0
> Reporter: Joshua
> Priority: Major
>
> Since I upgraded my apache beam sdk version to > 2.9.0, I have been noticing OOM exceptions while using the dataflow runner to write mutations to spanner. I have been using n1-standard-4 since version 2.9.0. On that version, it works. But on higher versions, I get the exception.
>
> The stackdriver logs is provided below
> {code:java}
> java.lang.OutOfMemoryError: Java heap space
> java.util.ArrayList.<init>(ArrayList.java:152)
> org.apache.beam.sdk.io.gcp.spanner.SpannerIO$GatherBundleAndSortFn.initSorter(SpannerIO.java:1056)
> org.apache.beam.sdk.io.gcp.spanner.SpannerIO$GatherBundleAndSortFn.startBundle(SpannerIO.java:1049)
> {code}
> I have a very basic PTransform for writing to Spanner:
> {code:java}
> SpannerIO.write().withInstanceId(options.getSpannerInstanceId()) .withDatabaseId(options.getSpannerDatabaseId()) .withProjectId(options.getProject()) .withFailureMode(SpannerIO.FailureMode.REPORT_FAILURES);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)