beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (BEAM-3089) Issue with setting the parallelism at client level using Flink runner
Date Tue, 18 Sep 2018 20:04:00 GMT

     [ https://issues.apache.org/jira/browse/BEAM-3089?focusedWorklogId=145457&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-145457
]

ASF GitHub Bot logged work on BEAM-3089:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Sep/18 20:03
            Start Date: 18/Sep/18 20:03
    Worklog Time Spent: 10m 
      Work Description: angoenka commented on a change in pull request #6426: [BEAM-3089]
Fix default values in FlinkPipelineOptions / Add tests
URL: https://github.com/apache/beam/pull/6426#discussion_r218574954
 
 

 ##########
 File path: runners/flink/src/test/resources/flink-conf.yaml
 ##########
 @@ -0,0 +1 @@
+parallelism.default: 23
 
 Review comment:
   nit: new line

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 145457)
    Time Spent: 1h 50m  (was: 1h 40m)

> Issue with setting the parallelism at client level using Flink runner
> ---------------------------------------------------------------------
>
>                 Key: BEAM-3089
>                 URL: https://issues.apache.org/jira/browse/BEAM-3089
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink
>    Affects Versions: 2.0.0
>         Environment: I am using Flink 1.2.1 running on Docker, with Task Managers distributed
across different VMs as part of a Docker Swarm.
>            Reporter: Thalita Vergilio
>            Assignee: Grzegorz KoĊ‚akowski
>            Priority: Major
>              Labels: docker, flink, parallel-deployment
>             Fix For: 2.8.0
>
>         Attachments: flink-ui-parallelism.png
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> When uploading an Apache Beam application using the Flink Web UI, the parallelism set
at job submission doesn't get picked up. The same happens when submitting a job using the
Flink CLI.
> In both cases, the parallelism ends up defaulting to 1.
> When I set the parallelism programmatically within the Apache Beam code, it works: {{flinkPipelineOptions.setParallelism(4);}}
> I suspect the root of the problem may be in the org.apache.beam.runners.flink.DefaultParallelismFactory
class, as it checks for Flink's GlobalConfiguration, which may not pick up runtime values
passed to Flink, then defaults to 1 if it doesn't find anything.
> Any ideas on how this could be fixed or worked around? I need to be able to change the
parallelism dynamically, so the programmatic approach won't really work for me, nor will setting
the Flink configuration at system level.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message