You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Davor Bonaci (JIRA)" <ji...@apache.org> on 2017/03/06 21:47:33 UTC

[jira] [Commented] (BEAM-1631) Flink runner: submit job to a Flink-on-YARN cluster

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

Davor Bonaci commented on BEAM-1631:
------------------------------------

[~aljoscha], is this analysis correct? Am I off-base here?

If this sounds reasonable, how hard would it be to add it?

> Flink runner: submit job to a Flink-on-YARN cluster
> ---------------------------------------------------
>
>                 Key: BEAM-1631
>                 URL: https://issues.apache.org/jira/browse/BEAM-1631
>             Project: Beam
>          Issue Type: New Feature
>          Components: runner-flink
>            Reporter: Davor Bonaci
>            Assignee: Aljoscha Krettek
>
> As far as I understand, running Beam pipelines on a Flink cluster can be done in two ways:
> * Run directly with a Flink runner, and specifying {{--flinkMaster}} pipeline option via, say, {{mvn exec}}.
> * Produce a bundled JAR, and use {{bin/flink}} to submit the same pipeline.
> These two ways are equivalent, and work well on a standalone Flink cluster.
> Submitting to a Flink-on-YARN is more complicated. You can still produce a bundled JAR, and use {{bin/flink -yid <applicationid>}} to submit such a job. However, that seems impossible with a Flink runner directly.
> If so, we should add the ability to the Flink runner to submit a job to a Flink-on-YARN cluster directly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)