[
https://issues.apache.org/jira/browse/BEAM-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17122906#comment-17122906
]
Beam JIRA Bot commented on BEAM-6764:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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)
