[
https://issues.apache.org/jira/browse/BEAM-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132934#comment-17132934
]
Mai Nakagawa edited comment on BEAM-6764 at 6/11/20, 5:56 AM:
--------------------------------------------------------------
[~jleoirab] - Are you using [Streaming Engine|#dataflow-streaming-engine]? We
faced the same situation while using it. We could work this around by not using
Streaming Engine.
was (Author: [email protected]):
[~jleoirab] - Are you using [Streaming Engine|#dataflow-streaming-engine]]? We
faced the same situation while using it. We could work this around by not using
Streaming Engine.
> 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.9.0, 2.10.0, 2.11.0
> Reporter: Joshua
> Priority: P2
> Labels: stale-P2
>
> 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
(v8.3.4#803005)
