You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/09 17:07:02 UTC

[jira] [Commented] (BEAM-8191) Multiple Flatten.pCollections() transforms generate an overwhelming number of tasks

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

Beam JIRA Bot commented on BEAM-8191:
-------------------------------------

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.


> Multiple Flatten.pCollections() transforms generate an overwhelming number of tasks
> -----------------------------------------------------------------------------------
>
>                 Key: BEAM-8191
>                 URL: https://issues.apache.org/jira/browse/BEAM-8191
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-spark
>    Affects Versions: 2.12.0, 2.14.0, 2.15.0
>            Reporter: Peter Backx
>            Priority: P2
>              Labels: stale-P2
>          Time Spent: 3h 40m
>  Remaining Estimate: 0h
>
> The Flatten.pCollections() is translated into a Spark union operation. The resulting RDD will have the sum of the partitions in the originating RDDs.
> If you flatten 2 PCollections with each 10 partitions, the result will have 20 partitions.
> This is ok in small pipelins, but in our main pipeline, this means the number of tasks grows out of hand quite easily (over 500k tasks in one stage). This overloads the driver and crashes the process.
> I have created a small repro case:
> [https://github.com/pbackx/beam-flatmap-test]
>  
> A possible solution is to add a coalesce call after the union. We have been testing this and it seems to do exactly what we want, but I'm not sure if this fix is applicable for all cases. 
> I will open a PR for this so that you can review my proposed change and discuss whether or not it's a good idea.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)