You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/05/15 17:59:02 UTC

[jira] [Updated] (BEAM-1329) Improve default resource allocation in ApexRunner

     [ https://issues.apache.org/jira/browse/BEAM-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-1329:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> Improve default resource allocation in ApexRunner
> -------------------------------------------------
>
>                 Key: BEAM-1329
>                 URL: https://issues.apache.org/jira/browse/BEAM-1329
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-apex
>            Reporter: Thomas Weise
>            Priority: P3
>
> The runner currently works off the Apex defaults, which especially for memory leads to excessive resource requests when applied to the Beam situation with many small ParDo operators. The runner should populate the attributes that drive resource allocation when generating the logical DAG during pipeline translation in a way more appropriate for Beam pipelines.



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